[
https://issues.apache.org/jira/browse/MNG-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883466#comment-17883466
]
Tamas Cservenak commented on MNG-8130:
--------------------------------------
None of the Mojos are "aware" of their binding, they may provide default phase,
but even then they need to be bound. So I'd diss mojo declaration.
To me this is somehow orthogonal. Hence, having it in POM, after all, this is
build specific, build author wants to do this, and having this in POM would be
clear.
> Feature to replace plugin provided by lifecycle
> -----------------------------------------------
>
> Key: MNG-8130
> URL: https://issues.apache.org/jira/browse/MNG-8130
> Project: Maven
> Issue Type: New Feature
> Components: Plugins and Lifecycle
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0
>
>
> Lifecycle define plugins like G:A:V. We've seen several practices how to
> "replace" (usually core) plugin with some non-core one. This most often
> involves some hacks, like lifecycle participant, that "rewrites" model upon
> it is loaded. This is hacky.
> We need some clear way, to be able to replace plugins, like by providing some
> "instead of G:A:V I want to use G':A':V'" and maven should just obey. No
> tricks, no hacks, no fuss.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
