Hi Stephen, "Stephen Haberman" <[EMAIL PROTECTED]> wrote on 29/09/2002 11:24:37 PM:
> 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. The plugin's maven.xml should have goals to install the plugin into maven. > 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. Even better, someone could put the plugin up on ibiblio. > 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? Within the Torque project makes sense, as does within Maven, if it's of general interest. Regardless, having it in the ibiblio repository makes it easy for everyone. We really need a plugin-update/plugin-list goal for maven... > Thanks, > Stephen -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
