Jason van Zyl wrote: > Yo Dion, > > Not sure what you have in mind for the plugin plugin, but the reactor > that is now used to build our plugins could be used as a template. You > could push out a template for our plugin setup so that it could be used > elsewhere. The sourceforge repository could use it and individual users > could employ it for their own homegrown plugins.
It's nice to see that maven.xml files were factored out of specific plugins' directories, but I believe that a plugin plugin is the way to go. Some maven plugins are built outside maven proper and we expect this will be even more widespread in the future. > So there could be a little federation of plugin builds and they can all > be pushed to the repo. I've fixed the groupId bug so that should help > with this endeavour to i.e. pushing plugins in the right place. I read the above paragraph twice, but still can't grasp it. If it is of intrest to the general pulblic, please explain :) R. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
