I think the suggested solution encourages the anti-pattern of binding plugins to the parent pom instead of in the actual child project. MAven (and its plugins) is about best-practice and therefore we shouldn't do this.
What you can do is to define the binding in the pluginManagement section of the parent (with the appropriate configuration), and then in the child declare the binding by just specifying:

<plugin>
  <groupId>...</groupId>
  <artifactId>...</artifactId>
</plugin>
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to