Gregg says:
> And what build tasks are going to be so complicated? Odd jar packaging?
There will be all sorts of code generation steps (very possibly using XSLT and
other tools). Ant provides you with a good tool to script all of the steps into
one build cycle.
> Adding your own source files, you should be able to compile into a single
> directory with 'javac -d' command line(s). You should be able to package
> this directory into a jar, and 'go'. You should also be able to provide
> this directory in your classpath to JEMBuilder like tools and get a linked
> product.
In the spirit of Ted's "Graphic Wiring Tool", I want a single command to build
everything, and that will take more than one compile step, transform steps,
code generation, packaging and maybe more. It would also include the
platform-specific link step (eg. JEMBuilder). Ant can do all of that. And Ant is
integrated with almost every major IDE out there...so that's not an issue. I do
all my builds with Ant from within my editor these days, and it has definitely
simplified my life.
> It should not be necessary for developers to do any kind of manual steps
> to develop with the platform.
No need, since Ant is integrated with most IDE's out there. In fact, Ant is an
automation tool for complex builds (and wiring Embedlets, JAPL drivers,
adapters and the like into a runnable app WILL be complex).
> I am really against leaning against Ant for any configuration management
> that can also be done in the code itself where late binding can yield some
> other advantages.
Every other container-based server out there uses Ant to simplify the builds. I
don't think that Outpost will be any different.
Writing your own build sequencer is a bit silly, IMNSHO. You would just end
up developing the same functionality that Ant already has.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
|
