[
https://issues.apache.org/jira/browse/MNG-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly resolved MNG-6217.
-----------------------------------
Resolution: Not A Problem
Fix Version/s: (was: 3.5.1)
This is IMHO intended behaviour. In a parent pom you may want to define some
defaults to be included for specific executions but not want those executions
bound to the lifecycle unless needed.
I have used this feature. It works and I do not see it as a problem. Marking
this issue as such on the basis that three others agreed
> Creating a WARNING by using executions in pluginManagement
> ----------------------------------------------------------
>
> Key: MNG-6217
> URL: https://issues.apache.org/jira/browse/MNG-6217
> Project: Maven
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.5.0
> Reporter: Karl Heinz Marbaise
> Priority: Minor
>
> I can often observe that defining something like this in pluginManagement:
> {code:xml}
> <pluginManagement>
> <plugins>
> <plugin>...
> <executions>
> ....
> </executions>
> </plugin>
> </plugins>
> </pluginManagement>
> {code}
> which is superfluous and shut not being done.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
