>Learn to use your tools, people. Writing your own ant task is trivial, as is hooking it up 'live' (i.e. first building it, then >using it, all in one ant invocation). The whole point of ant has always been that you should NOT be programming in >it. Personally I strongly believe any sufficiently complicated build will ALWAYS end up requiring programming, which >means both ant and maven are probably misguided (if anything ant moreso because creating a list of sequential ant >tasks such as 'mkdir' and 'javac' feels rather eerily similar to programming). Both of those tools do however allow >you to write plugins. I strongly suggest you get to grips with that.
Do you write your shell scripts in XML? Why not? Even the guy who created ant (James Duncan Davidson) now thinks XML was a bad idea. Why continue down the painful path when better paths are available (buildr/gradle)? perhaps you haven't seen the insanity I've seen, so you don't fully appreciate how F'ed up an ant build can get. You can say 'then they are doing it wrong.' Maybe - but I see it done wrong over and over again. You think it's "trivial" to create an ant task. Well, it means switching contexts and writing another build script to build your build script's tasks. It's too heavy. Which is why these contorted constructs like ant contrib and the macro tasks exist. > > In regards to JSP/Velocity to mix config XML and source: Oh hell no. That's > a horrible idea. > Not convincing. You think adding loops and variables inside your JSP's HTML is a horrible idea? Same thing. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
