[
https://issues.apache.org/jira/browse/MRM-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Chesshir updated MRM-1921:
-------------------------------
Description:
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
com.myproject:mymodule jars are present. However, the owners of that artifact
have set up their CI to only keep a rolling snapshot, and version 2.1.3-270 has
been phased out.
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.
was:
When I run for example 'mvn package', there's a (indirect) dependency that
cannot be resolved; This the part of the pom that causes the problem:
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
<version>[1.4,)</version>
<scope>compile</scope>
</dependency>
This results in the following error issued by Maven:
No versions are present in the repository for the artifact with a range [1.4,)
commons-beanutils:commons-beanutils:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
If I browse the repository http://repo1.maven.org/maven2, the commons-beanutils
jars (several versions) are present.
So I assume Archiva cannot handle the range.
> Could not find artifact com.project:artifact:jar:2.1.3-270 in repo
> ------------------------------------------------------------------
>
> Key: MRM-1921
> URL: https://issues.apache.org/jira/browse/MRM-1921
> Project: Archiva
> Issue Type: Bug
> Components: Build
> Environment: Linux-x86-32; maven 2.0.8
> Reporter: John Chesshir
> Assignee: Brett Porter
>
> 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
> com.myproject:mymodule jars are present. However, the owners of that
> artifact have set up their CI to only keep a rolling snapshot, and version
> 2.1.3-270 has been phased out.
> 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)
