[ https://issues.apache.org/jira/browse/MNG-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167470#comment-16167470 ]
Chris Hennick commented on MNG-6284: ------------------------------------ What purpose would such a definition serve, if it wouldn't bind the plug-in to a lifecycle phase? > <executions> inside <pluginManagement> should raise a warning > ------------------------------------------------------------- > > Key: MNG-6284 > URL: https://issues.apache.org/jira/browse/MNG-6284 > Project: Maven > Issue Type: Bug > Affects Versions: 3.0.5 > Environment: Ubuntu 14.04.3 > Reporter: Chris Hennick > > When I was setting up my project's pom.xml, I was unaware that there was a > difference between project/build/pluginManagement/plugins and > project/build/plugins. These StackOverflow questions indicate I'm not the > only one who was confused: > * > https://stackoverflow.com/questions/18557245/not-able-to-bind-plugin-goals-to-maven-lifecycle-phases > * > https://stackoverflow.com/questions/23785443/binding-to-lifecycle-in-maven-does-not-work-on-failsafe-and-integration-test > If we have to have such a confusing schema, then can we please at least raise > a warning when the confusion inevitably occurs, given how easy it is to > detect (since AFAICT there'd be no reason to put an executions tag inside > pluginManagement/plugins/plugin)? -- This message was sent by Atlassian JIRA (v6.4.14#64029)