Cool; I've had almost the same plugin that I had been meaning to submit, and kinda thought I did, but don't remember exactly.
Two things: 1) If a build-torque.xml file is included in the plugin, then the user doesn't need any Torque cruft in their source tree, not even the build-torque.xml. 2) I haven't picked up how post-maven-install plugin installation goes, but I was wondering if just having this plugin over in Torque would be better as then we could modify the build-torque.xml when needed and easily synchronize it with our code base. I thought I picked up from Jim Birchfield that if we have a torque-plugin.jar, people could download it from the Torque site, put it in maven.home/plugins, maven would auto-extracted it (?), and then have use of the torqure:xxx goals. Does this sound right? And is the best practice for plugin distribution currently/going to be keeping the plugin within the Torque project or having everything in maven/that-sf-project? Thanks, Stephen > -----Original Message----- > From: Markus M. May [mailto:[EMAIL PROTECTED]] > Sent: Sunday, September 29, 2002 6:54 AM > To: Turbine Maven Developers List > Subject: Torque plugin > > > >Hello, > > I just added a new plugin to my maven install. It is a plugin which > delegates goals to a specified torque buildfile (by default it is the > build-torque.xml in the root of your project. If you would like to use > another file you can specify > maven.torque.buildFile in your project.properties. > > Hope this helps. > > > ---+++--------------------+++---------------------+++--- > Markus M. May > [EMAIL PROTECTED] > > Provide you with free J2EE projects > > Please use my public key at: > http://www.javafreedom.org/mmay_javafreedom_org.key > ---+++--------------------+++---------------------+++--- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
