[
https://jira.codehaus.org/browse/MNG-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354032#comment-354032
]
F Carlsen commented on MNG-5588:
--------------------------------
This would be great improvement and would helps share plugin configuration and
standards across projects.
At the moment, the only way of sharing plugin configuration is through
inheritance. Unfortunately, this isn't always feasible, and relying on
inheritance for sharing configuration that only some children are going to need
is a bad practice (e.g. violates Liskov's substition principle). Composition
would be better than Inheritance for configuration anyway.
In a muti-module project, you will get a warning if you're trying to use parent
pom's from different inheritance hierarchies, which says it may be disallowed
in a future release, so there's really decent alternatives today and I hope
this feature gets prioritized.
> Scope import in pluginManagement
> --------------------------------
>
> Key: MNG-5588
> URL: https://jira.codehaus.org/browse/MNG-5588
> Project: Maven
> Issue Type: Wish
> Components: Dependencies, FDPFC
> Affects Versions: 3.1.1
> Reporter: Romain N
>
> 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
(v6.1.6#6162)
