|
Brian,There is one very good reason. Building the final product with ant allows somebody else on another machine to build it at anytime, perhaps even automated based on sources in CVS.
There's a couple of comments you made that sparked my interest:
* Eclipse (WDSC) for code developmentI've never understood why developers using Eclipse still use Ant? You
* Apache Ant for building and deploying
.... I bundled all my complied classes into Jar files
don't need to perform a distinct "build" step since Eclipse automatically
compiles every .class file as you changes its source file. So you create
your JARs just by highlighting them, picking File-Export and exporting the
JAR. The only reasons I can think of for using Ant would be:
a) If you had a huge number of JARs and so exporting them one by one was
just too tedious.
b) If you needed your JARs to be different for development & production
environments (which to me is a really bad idea, but I've known one
developer who was quite serious about wanting to do this).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.