On Mon, Nov 19, 2001 at 12:47:45PM +0200, Leon Breedt wrote: > On Mon, Nov 19, 2001 at 09:36:39PM +1100, Jeff Turner wrote: > > I was wondering, how do people feel about developing "common", > > "universal", "generic" build.xml scripts for common needs? > i've had this exact need. > > > My very first build.xml was copied from an Apache project, and hacked to > > meet my needs. Subsequent projects were all cut-and-paste affairs. Over > > time, as I noticed that most projects are pretty similar, I formalized > > this by creating a "generic" build.xml, and an associated template > > project structure. > guess what i did this weekend :) my idea was to also supply > a skeleton generator, which would prompt for some > project-specific information, and perform mangling of the > template (token substitution), the end result being a > compilable skeleton app.
Sounds like an interesting addition to the "solution space". ['ant -projecthelp' output] > > one addition i'd want: > > 'fetch-build-depends' > - download application build dependencies > used Debian Linux's apt-get build? the > very same idea. > > the reason being that i don't generally put JARs except > required to bootstrap the build system into > source control systems, being of the pristine source > school. Oo yes I forgot.. a template build system also lets new users play with the latest techniques like this. Ever wanted to try JJAR (auto-jar-download-thingy), but never had the time? As soon as Geir or someone contributes a demo system, the learning curve is dramatically decreased. One trailblazer does the work and the rest of us follow and learn at a gentler pace. It's how civilizations advance; it's how Ant can advance :) --Jeff > regards, > leon. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
