maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5942) Maven 3.3 Fails with Parent Version Range
Date Thu, 03 Dec 2015 20:39:10 GMT

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

Steve Wall commented on MNG-5942:
---------------------------------

Thanks for looking into this. I think this was a problem with our maven-metadata.xml. We changed
our versioning scheme from just a number to the dot notation. I think the fact they were both
listed caused mvn to pick a version I wasn't expecting. This may have become stricter between
3.2 and 3.3, as it seemed to work with 3.2. 

> Maven 3.3 Fails with Parent Version Range
> -----------------------------------------
>
>                 Key: MNG-5942
>                 URL: https://issues.apache.org/jira/browse/MNG-5942
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.3.3
>         Environment: Maven home: /opt/apache-maven-3.3.3
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /etc/alternatives/jdk1.8.0_60/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-123.el7.x86_64", arch: "amd64", family: "unix"
>            Reporter: Steve Wall
>            Assignee: Jason van Zyl
>              Labels: maven
>
> Specifying a version range for the parent does not seem to work with 3.3.3. I verified
it does work with 3.2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message