[jira] [Commented] (MNG-5588) Scope import in pluginManagement

["Jeff Thomas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547287#comment-16547287 ] 

Jeff Thomas commented on MNG-5588:
----------------------------------

I would also love to see this feature.

I just implemented a 'dependencyManagement' import POM for all of the Axis2 dependencies that we need to keep synchronized over multiple projects without parent-inheritence.

However, Axis2 also provides several Maven Plugins which I would like to centrally manage the versions and base-configurations for as well.

The Mixin plugin still requires you to define plugin versions in the parent-poms...ideally I would want to do that centrally as with the dependencyManagement import POM.

> Scope import in pluginManagement
> --------------------------------
>
>                 Key: MNG-5588
>                 URL: https://issues.apache.org/jira/browse/MNG-5588
>             Project: Maven
>          Issue Type: Wish
>          Components: Dependencies, FDPFC
>    Affects Versions: 3.1.1
>            Reporter: Romain N
>            Priority: Major
>
> I can do this in dependencyManagement to define dependencies versions:
> {code}
> <dependency>
> 	<groupId>test</groupId>
> 	<artifactId>test</artifactId>
>         <version>1</version>
>        <scope>import</scope>
>        <type>pom</type>
> </dependency>
> {code}
> It could be great to can do the same things in pluginManagements to define version plugin and default behavior.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)