[
https://issues.apache.org/jira/browse/MNG-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966459#comment-15966459
]
Robert Scholte commented on MNG-6217:
-------------------------------------
I know situations where adding execution blocks make sense. If you have a
company parent and you have plugins which should be executed pased on the type
of project, then it is often easier to do this setup, so developers only have
to specify the plugins groupId+artifactId to make that plugin part of the build
lifecycle. This is often done when having a hierarchy of parents is unpractical.
> 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
> Fix For: 3.5.1
>
>
> 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)
