Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[higgins-dev] Re: IdAS build.xml & buildaux.xml
  • Able to manage from within eclipse without dual editing build files
  • Able to build from the command line
  • Should be no absolute class names
  • Shouldn't require eclipse-specific jar files (only stated dependencies)
  • Should build when eclipse is not installed
  • What targets are required?
    • jar for any consumable component
    • war file for WS deployable components
    • debug versus binary
    • javadoc
    • eclipse plugin target
      • this probably requires ecplise to be deployed -- hopefully this can just be a target that is selectable
To address the first goal, we had to use two build files for each project.  build.xml is an eclipse-generated build (Project, Export, Build File) and thus we cannot hand-edit it.  buildaux.xml is auto-included when build.xml is generated by eclipse.  It is in this build file where we place any custom targets.
 
Yes, if you can add a target to buildaux.xml to produce an eclipse plugin .zip file, that would be good.
 
Thanks,
Jim


>>> Evgeniy Vyborov <evyborov@xxxxxxxxxxxxxx> 2/20/07 9:08 AM >>>
Hi Jim.

I was just thinking about your new IdAS build files (build.xml and
buildaux.xml). I've found that using these Ant files I can create jar
files, generate javadocs etc., such as it was before with previous
version of build.xml. And all resulting files are put to new
directories. That's great. But I just try to understand: what else goals
(except changed build directories) did you pursue?

I've found a way to change IdAS build file in order to provide the
possibility of simple generating complete Eclipse plugin *.zip file from
command line (anyone will be able to do it). Does it have sense for us?

Thanks
- Evgeniy

Back to the top