Jason van Zyl <[EMAIL PROTECTED]> wrote on 22/10/2003 04:40:37 PM: [snip good stuff]
> 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. It shouldn't require that the plugins have maven as their groupId, i.e. if it's javaapp:blah, and the javaapp plugin is remote_repo/maven-plugins/plugins/javaapp-plugin-1.5.jar it should still be able to find it. > 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. Plugin test projects are able to be decoupled from the bootstrap, and can be tested using the plugin plugin. That's one option. At the moment we're waiting on Brett checking in a new PluginManager so that the download can be slotted in there, right? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
