You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/05/27 18:56:00 UTC
[jira] [Updated] (MNG-8130) Feature to replace plugin provided by lifecycle
[ https://issues.apache.org/jira/browse/MNG-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak updated MNG-8130:
---------------------------------
Summary: Feature to replace plugin provided by lifecycle (was: Ability to replace plugin provided by lifecycle)
> 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
>
> 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)