You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Joseph Heck (JIRA)" <ji...@codehaus.org> on 2008/03/20 20:57:46 UTC
[jira] Commented: (MRM-675) Problem with version ranges: "no
versions are present in the repository for the artifact with a range"
[ http://jira.codehaus.org/browse/MRM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128068 ]
Joseph Heck commented on MRM-675:
---------------------------------
I've also run into this problem with Maven 2.0.8 (Win32) when requesting a locked down version of dom4j:
<dependency>
<groupId>dom4j</groupId>
<artifactId>dom4j</artifactId>
<version>[1.6.1]</version>
</dependency>
But other requests using this format appear to work properly:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>[3.8.1]</version>
</dependency>
> Problem with version ranges: "no versions are present in the repository for the artifact with a range"
> ------------------------------------------------------------------------------------------------------
>
> Key: MRM-675
> URL: http://jira.codehaus.org/browse/MRM-675
> Project: Archiva
> Issue Type: Bug
> Components: build
> Affects Versions: 1.0
> Environment: Linux-x86-32; maven 2.0.8
> Reporter: Chris Bonami
> Fix For: 1.1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira