Still, I bet that not needing "build-torque.xml" would justify using maven. At least for me. :-)
And remember the original discussion. The current scheme has some limitations that hopefully the plugin will not have. e.g. Configuring serveral databases and several database types. -- Humberto -----Original Message----- From: Stephen Haberman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 21, 2002 5:18 PM To: 'Turbine Torque Developers List' Subject: RE: torque maven plugin > Yeah, I understand what the plug-in does, but my appliation doesn't > use Maven and shouldn't be required to. I'll adopt it when I'm (and > it's) good and ready, and not before. ;) I never meant to insinuate Torque users would have to use Maven or that we would get rid of the build-torque.xml. If people want to continue calling build-torque.xml directly and editing it as needed to fit their build process, that's fine. What I'd like to move towards is having Torque integrated into the build process (any build process) that calls build-torque.xml when needed and everything is controlled via build properties, there by hopefully hiding the build-torque.xml from users as much as possible. The uptodate code I just checked in is a reflection of this. When I said projects could get rid of build-torque.xml, I meant only for projects that choose to use the discussed maven plugin, which would have it's own copy of build-torque.xml, there by hiding it even more from the user. Sorry if I didn't qualify the 'getting rid of build-torque.xml' thing better when I stated it a few emails ago. - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
