[
http://jira.codehaus.org/browse/MRM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143730#action_143730
]
Stefan Hübner commented on MRM-675:
-----------------------------------
{quote}
Could you try this in Archiva 1.1? I think this is already fixed in that
version.
{quote}
Frankly not. The addressed behaviour is still present.
What happens e.g. if you have a dependency to slf4j-api like this:
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>[1,2)</version>
</dependency>
is, that Maven returns the following:
No versions are present in the repository for the artifact with a range [1,2)
org.slf4j:slf4j-api:jar:null
I tried this using a fresh copy of Archiva 1.1 with a proxy connector for
Central Repo set up. This proxy connector is configured as mirrorOf central in
my maven settings. Now after maven has run I find the following files in
archiva's repo for /org/slf4j/slf4j-api:
* maven-metadata-central.xml
* maven-metadata-central.xml.md5
* maven-metadata-central.xml.sha1
* maven-metadata.xml
* maven-metadata.xml.md5
* maven-metadata.xml.sha1
{{maven-metadata-central.xml}} is OK, but {{maven-metadata.xml}} isn't. It
looks like this:
<metadata>
<groupId>org</groupId>
<artifactId>slf4j</artifactId>
<version>slf4j-api</version>
</metadata>
So, all versioning information is lost in this metadata-file.
Since Maven apparently fetches this file, _local repositories will be getting
screwed gradually_. So this issue is a *blocker* for everybody using version
ranges in its POMs.
> 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.x
>
>
> 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
