Sorry, I've not read this entire thread, but have a quick comment...
This idea of plugin packs could easily be extended to the more
generic pom inclusion stuff I've talked about previously. There
other things besides plugin version binding that could be bundled up
into a reusable package (like a common IDE configuration profile for
example).
Sure, grouping up plugins bound to specific versions is very handy
and should help simplify many projects (and even help reduce build
fragility), but IMO it would be a whole lot nicer to see a general
import some pom (by artifact:groupId:version) and merge the contents
into the current poms for execution.
--jason
On Sep 1, 2007, at 4:35 AM, Hervé BOUTEMY wrote:
Le samedi 1 septembre 2007, Brian E. Fox a écrit :
I think we can do this just by generating a sample pluginManagement
snippet on the site somewhere. I don't think anything fancy is
needed,
simply providing the snipet so someone can copy and paste will be
more
than sufficient. Having it generated with the current latest release
would then make it a good starting point as most people would want
the
latest by default and would only resort to reverting if they hit a
problem with a particular plugin.
+1
IMHO, a link to it should be added to http://maven.apache.org/
plugins/,
because it's the same information in another format.
Plugins groups (or packs) are already organized here, and can be
represented
in the pluginManagement snippet as XML comments
WDYT?
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
