[
https://jira.codehaus.org/browse/MNG-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-2805:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Provide mechanism for suppressing inherited/injected/mapped mojo binding
> ------------------------------------------------------------------------
>
> Key: MNG-2805
> URL: https://jira.codehaus.org/browse/MNG-2805
> Project: Maven
> Issue Type: New Feature
> Components: POM
> Affects Versions: 2.0.4
> Reporter: John Casey
>
> In some cases, a mojo should be suppressed from the build process. If this
> mojo binding comes from a parent POM or a lifecycle mapping, it's not
> possible to simply comment out that mojo binding. Currently this sort of
> functionality is left to the individual plugins to implement as parameters
> that cause each mojo to bow out. This use case is common enough in large
> development environments (for addressing the 80% with no customization, but
> allowing the remaining 20% the control to use the same parent POM with
> subtractions) to warrant a built-in suppression/disabling functionality.
> Suppression should be available by plugin or by plugin-execution. To suppress
> bindings from the packaging-mapping, the default executionId 'default' can be
> used.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
