[ 
https://issues.apache.org/jira/browse/MNG-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883465#comment-17883465
 ] 

Guillaume Nodet commented on MNG-8130:
--------------------------------------

I see two different ways to implement this:
* either in the POM / plugin configuration somehow
* in the plugin itself on the mojo declaration

Thoughts  ?

> 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)

Reply via email to