[
https://jira.codehaus.org/browse/MENFORCER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362608#comment-362608
]
Karl-Heinz Marbaise commented on MENFORCER-222:
-----------------------------------------------
After checking this is an regression between 1.3 and 1.3.1 which reduces the
problem into a more limited way.
> RequireSameVersion rule regression between 1.3 and 1.4
> ------------------------------------------------------
>
> Key: MENFORCER-222
> URL: https://jira.codehaus.org/browse/MENFORCER-222
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Rule API
> Affects Versions: 1.4
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T22:58:10+02:00)
> Maven home: C:\Tools\Maven\3.2.3
> Java version: 1.7.0_55, vendor: Oracle Corporation
> Java home: C:\Tools\Java\jdk1.7.0_55\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Benoit Maggi
> Attachments: parent.zip
>
>
> I tried a simple example of requiresameversion rule and it's failing fine in
> 1.3 version but not failing in 1.4
> <requireSameVersions>
> <dependencies>
> <dependency>org.eclipse:*</dependency>
> </dependencies>
> </requireSameVersions>
> Use the attached file to test :
> mvn validate => build success
> mvn validate -P previousversion => build failed
> It is expected to failed in both use case.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
