You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/07/15 10:55:00 UTC

[jira] [Created] (MENFORCER-388) Extends RequirePluginVersions with banMavenDefaults

Robert Scholte created MENFORCER-388:
----------------------------------------

             Summary: Extends RequirePluginVersions with banMavenDefaults
                 Key: MENFORCER-388
                 URL: https://issues.apache.org/jira/browse/MENFORCER-388
             Project: Maven Enforcer Plugin
          Issue Type: Improvement
            Reporter: Robert Scholte
            Assignee: Robert Scholte
             Fix For: 3.0.0


Since Maven 2.0.9 Maven comes with a set of predefined versions in the [super POM|http://maven.apache.org/ref/current/maven-model-builder/super-pom.html] and the [default lifecycle bindings|http://maven.apache.org/ref/current/maven-core/default-bindings.html]
When using these plugins without explicit giving it a version in your pom, the build depends on a specific Maven version.
Best practice is to lock these plugins in your pom, hence these Maven defaults should be banned.
When using the Maven Wrapper, you have already locked the Maven version, in which case you don't need to lock these versions.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)