[EMAIL PROTECTED] wrote on 07/02/2002 05:35:44 PM: Glenn Stampoulis writes: >> Absolutely. That's my current gripe with both Maven and Centipede. Neither >> is as flexible as straight ant. For example in Maven b4 simply specifying >> some system property for my tests cases requires me to modify Maven >> directly. Not really desirable. >Glenn, that's gotta be a bug. Can you give some more detail on the Maven lists?
I'm pretty sure it's not a bug. It just wasn't considered or was considered and found to be hard to implement. Take a look at the build file for the test plugin to see what I mean. >> What's the import tag? I couldn't find it in the documentation >Ditto. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10276 >> Ant has has few limitations as a build system. It does tend to bog down for >> complicated builds. Just look at the hoops you have to go through to do >> conditional logic so I guess I can understand why Maven might have headed in >> that direction. Whether it's going to turn out to be a good move remains to >> be seen. Ant has a large established userbase with a large range of really >> nifty ready to use tasks. >The good thing about Jelly is that it can also execute Ant scripts. I'd be interested in learning more about what problems you believe Jelly solves that Ant was unable to. Regards, Glen Stampoultzis (TriNexus Pty Ltd) Fixed:+61 3 9753-6850 Mob:+61 (0)402 835 458 ICQ: 62722370 EMail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
