>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).
One of the IDEs I use is the vi editor, and it doesn't do integrated commands
directly.
>> 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.
Ahh, but mine doesn't, so don't say all :-)
I am not trying to make an argument against Ant here. I am trying to make an
argument against unnecessary complications in the build step just because.
Tools that provide automation become crutches quickly, and if you don't think
about what you're doing, you can create such a dependency that suddenly your
software architecture and many other things are suddenly governed by the
tools, instead of the tools facilitating a good architecture...
-----
gr...@cy... (Cyte Technologies Inc)
|
