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 2023/06/11 16:38:00 UTC
[jira] [Assigned] (MNG-7807) Update Super POM plugins
[ https://issues.apache.org/jira/browse/MNG-7807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak reassigned MNG-7807:
------------------------------------
Assignee: Tamas Cservenak
> Update Super POM plugins
> ------------------------
>
> Key: MNG-7807
> URL: https://issues.apache.org/jira/browse/MNG-7807
> Project: Maven
> Issue Type: Task
> Components: Plugins and Lifecycle
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 3.9.3
>
>
> Super POM currently defines 4 plugins (removed in Maven 4), that are actually Maven 2.x (!) plugins.
> Those are (with current latest versions):
> {noformat}
> antrun: 1.3 -> 3.1.0
> assembly: 2.2-beta-5 -> 3.6.0
> dependency: 2.8 -> 3.6.0
> release: 2.5.3 -> 3.0.1 {noformat}
> Among other things, this is the reason why users with "empty POM" end up with plugin validation warnings (as all these plugins warn, as they are Maven2 plugins, not Maven 3).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)