My primary concern is as follows. Say there is a version 1.1 of a plugin specified in the pluginManagement section and that was joined with a plugin of version 1.0. The plugin configuration information may be completely incompatible. Also if you do the key off of version, you can define the same plugin with different versions and different configs in the same pluginManagement section.
Shane On Sat, Nov 29, 2008 at 4:04 PM, Benjamin Bentmann < [EMAIL PROTECTED]> wrote: > Hi, > > In the light of MNG-3866 [0], Shane and I had a short discussion what > should be the right behavior during model inheritance for handling plugin > definitions with different versions. Apparently, that is something to > discuss in the context of the community ;-), so please comment. > > In Maven 2.x, <plugin> sections are merged based on the plugin key which > consists of groupId:artifactId, i.e. does not contain the plugin version > (c.f. ModelUtils.mergePluginLists()). This differs from Maven 3.x trunk > where <plugin> definitions are currently only merged if groupId, artifactId > and version match (c.f. ArtifactModelContainer.containerAction()). > > So, what's the proper behaviour? > > > Benjamin > > > [0] http://jira.codehaus.org/browse/MNG-3866 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
