[
http://jira.codehaus.org/browse/MRM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153037#action_153037
]
Kaloyan Enimanev commented on MRM-675:
--------------------------------------
Hey guys,
we're using Archiva 1.1.3, where the problem still persists (occurs with the
very same {{slf4j-api}} depedency) and as Stefan already mentioned this is a
blocker for us. Removing version ranges from our POMs is not an option, so I
was wondering:
* How do you get round the issue ?
* Is there a patch we could apply ?
Thank you very much in advance,
Kaloyan
> 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.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
