[
https://issues.apache.org/jira/browse/MNG-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605433#comment-16605433
]
Dmitry Ovchinnikov commented on MNG-5588:
-----------------------------------------
The dependency version importing is a killer feature of Maven, it's a
"declarative way" the Maven belongs to. It would be very useful to have
something like that for plugins. Could it be like that?
{code:xml}
<dependencyManagement>
<dependency>
<groupId>some-group-id</groupId>
<artifactId>some-artifact-id</artifactId>
<version>a-version</version>
<scope>import-plugins</scope>
<type>pom</type>
</dependency>
</dependencyManagement>
{code}
So, we could have different scopes without changing the POM model:
"import-dependencies" (an alias to "import"), "import-plugins",
"import-properties" and so on.
> Scope import in pluginManagement
> --------------------------------
>
> Key: MNG-5588
> URL: https://issues.apache.org/jira/browse/MNG-5588
> Project: Maven
> Issue Type: Wish
> Components: Dependencies, FDPFC, POM
> 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)
