[
https://issues.apache.org/jira/browse/MNG-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise moved MPOM-138 to MNG-6087:
-----------------------------------------------
Affects Version/s: (was: MAVEN-30)
3.3.1
Component/s: (was: maven)
core
Key: MNG-6087 (was: MPOM-138)
Project: Maven (was: Maven POMs)
> Version ranges stop build if minimum version is not available
> -------------------------------------------------------------
>
> Key: MNG-6087
> URL: https://issues.apache.org/jira/browse/MNG-6087
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.1
> Reporter: John Chesshir
>
> When I run for example 'mvn package', there's a dependency that cannot be
> resolved during Maven's pom.xml evaluation faze; This is a mockup of the part
> of the pom that causes the problem:
> <dependency>
> <groupId>com.project</groupId>
> <artifactId>artifact</artifactId>
> <version>[2.1.3-270,)</version>
> </dependency>
> This results in the following error issued by Maven:
> Failed to execute goal on project MyProject: Could not resolve dependencies
> for project com.myproject:mymodule:jar:1.3.9-240: Could not find artifact
> com.project:artifact:jar:2.1.3-270 in myRepo
> (http://myrepo.local:7392/artifactory/repo)
> If I browse the Artifactory repository
> http://myrepo.local:7392/artifactory/repo, there are several versions of
> com.myproject:mymodule jars present. However, the owners of that artifact
> have set up their CI to only keep a rolling snapshot, and version 2.1.3-270
> is no longer available.
> We are using Maven 3.2.5. It seems that Maven should not require any of the
> named versions in a version range to actually be present before it can see
> whether any versions exist that do fit in the range. We only want to have to
> update our minimum version when there is a breaking change that we have to
> address, not just when the publishers decide to remove the minimum version
> from availability.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
