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

Tibor Digana commented on MNG-6169:
-----------------------------------

Docker users use old version of Surefire and this results in misunderstandings 
of what (file system bugs) is fixed and what is not.

The users do not know that we made any release.

So. We spend our time with release new versions and the users do not know. Even 
they do not feel comfortable to update tons of plugins in their POM and another 
situation happens that the companies build rules where a list of versions is 
defined and they do not have reason to do it. Only because of rules which 
created this list upon that time when the historical versions were deployed on 
Maven Central. What makes sense to me is to run a test with Maven and the 
latest plugins, and then these should appear in {{{{default-bindings.xml}}}}.

> 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: Issues to be reviewed for 3.x
>
>
> 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 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)

Reply via email to