> I would imagine a torque.xml like this. May be something similary to what > they did in Maven with jelly would be great. Sincerly, every time I look at > build-torque.xml I get a headache. And now is much better than it used to > be.
I agree with build-torque.xml not being the most user friendly. I really want to move away from people having to edit it and having everything driven from properties. Which I think CVS head does pretty well. As far as maven is concerned, I was thinking a Torque plugin might be in order, with the benefit that people building projects with maven would then not even need the build-torque.xml file in their project directories. All of the Torque classes/templates would be read from the classpath/maven.repo.local and the build-torque.xml would be shipped with the maven plugin that delegated to it. I haven't a clue about maven plugins, but I trust Jason & co. to make it pretty slick and easy to make them. Does this sound like a cool feature? On a side note, I don't think we could move to a pure-maven/jelly Torque. Unless maven gets as wide distribution as ant, we'll still have to have some variation of build-torque.xml around. Thanks, Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
