> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 08:41 > To: Maven Developers List > Subject: Re: Moving plugins
[snip] > The touchstone could probably even go. I'm going to out a proposal where > the names of goals are done in such a way that we follow the once > established convention of <plugin>:<action> (e.g. jar:build). With this > the goal is linked to it's plugin explicity. It would be easy to detect > whether the plugin for that goal is present so it could be downloaded > and this method would scale to any number of plugins. I'll whip it off > tomorrow it's only a few paragraphs. > > Then this list above will be moot as it won't matter where the plugins > are. Also a testing method that is not bound to the bootstrap is > necessary so that we and others can test plugins correctly against any > number of desired versions not just CVS HEAD. +1 Ah. That would be great! With that in place, I'll be happy to move the cactus plugin in the cactus project! Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
