Rupert Madden-Abbott created MENFORCER-327:
----------------------------------------------

             Summary: Regression possibly caused by MENFORCER-281
                 Key: MENFORCER-327
                 URL: https://issues.apache.org/jira/browse/MENFORCER-327
             Project: Maven Enforcer Plugin
          Issue Type: Bug
          Components: Standard Rules
    Affects Versions: 3.0.0-M2
            Reporter: Rupert Madden-Abbott


I have a multi-module project, the parent pom of which inherits from 
spring-boot-starter-parent. It also enables maven-enforcer. The Sprint Boot pom 
defines explicit versions for all of these plugins:
 * org.apache.maven.plugins:maven-clean-plugin
 * org.apache.maven.plugins:maven-failsafe-plugin
 * org.apache.maven.plugins:maven-dependency-plugin
 * org.apache.maven.plugins:maven-install-plugin
 * org.codehaus.mojo:versions-maven-plugin
 * org.apache.maven.plugins:maven-deploy-plugin

 

This worked fine under 3.0.0-M1. However, since 3.0.0-M2, I get the following 
build failure from maven-enforcer:

[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequirePluginVersions 
failed with message:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not 
allowed )
org.apache.maven.plugins:maven-clean-plugin. The version currently in use is 
3.1.0
org.apache.maven.plugins:maven-failsafe-plugin. The version currently in use is 
2.22.1
org.apache.maven.plugins:maven-dependency-plugin. The version currently in use 
is 3.1.1
org.apache.maven.plugins:maven-install-plugin. The version currently in use is 
2.5.2
org.codehaus.mojo:versions-maven-plugin. The version currently in use is 2.7
org.apache.maven.plugins:maven-deploy-plugin. The version currently in use is 
2.8.2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to