[
https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6169:
-------------------------------
Description:
This is an umbrella ticket to track work up packaging plugin bindings version
upgrades. The file is
{{maven-core/src/main/resources/META-INF/plexus/default-bindings.xml}}.
The work is structured in subtasks per packaging type.
This requires MNG-6562 first, to avoid users to blindly rely on these versions,
then be impacted by a change while changing Maven version used without really
understanding that they should lock down their plugin versions in their poms
(eventually via parent)
This table will go away as soon as all tickets will have been created:
Regular plugin update to absorb changes if plugin version is not specified in
the client POM.
||groupId||artifactId||[previous
version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
version||
|-org.apache.maven.plugins-|-maven-clean-plugin-|-2.5-|MNG-6548|
|-org.apache.maven.plugins-|-maven-site-plugin-|-3.3-|MNG-6548|
|org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1|
|org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1|
|org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2|
|org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1|
|org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3|
|org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2|
|org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (already 3.0+)|
|org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0|
|org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0|
|org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1|
|org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (needs 3.0 release (!))|
was:
This is an umbrella ticket to track work up packaging plugin bindings version
upgrades. The file is
{{maven-core/src/main/resources/META-INF/plexus/default-bindings.xml}}.
The work is structured in subtasks per packaging type.
This requires MNG-6562 first, to avoid users to blindly rely on these versions
then be impacted by a change while changing Maven version used without really
understanding that they should lock down their plugin versions in their poms
(eventually via parent)
This table will go away as soon as all tickets will have been created:
Regular plugin update to absorb changes if plugin version is not specified in
the client POM.
||groupId||artifactId||[previous
version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
version||
|-org.apache.maven.plugins-|-maven-clean-plugin-|-2.5-|MNG-6548|
|-org.apache.maven.plugins-|-maven-site-plugin-|-3.3-|MNG-6548|
|org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1|
|org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1|
|org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2|
|org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1|
|org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3|
|org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2|
|org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (already 3.0+)|
|org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0|
|org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0|
|org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1|
|org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (needs 3.0 release (!))|
> Packaging plugin bindings version updates
> -----------------------------------------
>
> Key: MNG-6169
> URL: https://issues.apache.org/jira/browse/MNG-6169
> Project: Maven
> Issue Type: Improvement
> Components: core, Dependencies
> Affects Versions: 3.3.9
> Reporter: Christian Schulte
> Assignee: Michael Osipov
> Priority: Minor
> Fix For: 3.7.0-candidate
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is an umbrella ticket to track work up packaging plugin bindings version
> upgrades. The file is
> {{maven-core/src/main/resources/META-INF/plexus/default-bindings.xml}}.
> The work is structured in subtasks per packaging type.
> This requires MNG-6562 first, to avoid users to blindly rely on these
> versions, then be impacted by a change while changing Maven version used
> without really understanding that they should lock down their plugin versions
> in their poms (eventually via parent)
> This table will go away as soon as all tickets will have been created:
> Regular plugin update to absorb changes if plugin version is not specified in
> the client POM.
> ||groupId||artifactId||[previous
> version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
> version||
> |-org.apache.maven.plugins-|-maven-clean-plugin-|-2.5-|MNG-6548|
> |-org.apache.maven.plugins-|-maven-site-plugin-|-3.3-|MNG-6548|
> |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1|
> |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1|
> |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2|
> |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1|
> |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3|
> |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2|
> |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (already 3.0+)|
> |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0|
> |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0|
> |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1|
> |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (needs 3.0 release (!))|
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
