[jira] Commented: (MNG-2704) Range check don't work correct

["fabrizio giustina (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-2704?page=comments#action_82808 ] 
            
fabrizio giustina commented on MNG-2704:
----------------------------------------

for version ranges to work you have to be sure that metadata in the repository are ok.
Your example should work if the remote (or local if you didn't downloaded such dependency) repository contains a metadata like:
http://repo1.maven.org/eclipse/org/eclipse/equinox/org.eclipse.equinox.common/maven-metadata.xml

If you are using version range you need to have good metadata, which usually means never manually copy anything to the local repository.

> Range check don't work correct
> ------------------------------
>
>                 Key: MNG-2704
>                 URL: http://jira.codehaus.org/browse/MNG-2704
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.4
>         Environment: OS: Windows XP
> Java: jdk1.5.0_10
>            Reporter: Stephan Zehrer
>            Priority: Minor
>         Attachments: demo.zip
>
>
> I included the following part in my pom.xml:
> 		<dependency>
> 			<groupId>org.eclipse.jface</groupId>
> 			<artifactId>org.eclipse.jface</artifactId>
> 			<version>3.2.0</version>
> 		</dependency>	
> I always get the following error 
> No versions are present in the repository for the artifact with a range [3.2.0,4.0.0)
>   org.eclipse.equinox:org.eclipse.equinox.common:jar:null
> But I am sure that version 3.2.0 is available in the repository. 
> If I define only a dependency on this library like this
> 		<dependency>
> 			<groupId>org.eclipse.equinox</groupId>
> 			<artifactId>org.eclipse.equinox.common</artifactId>
> 			<version>3.2.0</version>
> 		</dependency>
> it works!
> If I define both it will not work. Why?
> According 
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
> It could be forced by this
> My current workaround is the exclusion definition.
> What did I wrong or is this a bug?
> See the demo I Attached, you need the Eclipse repository.

-- 
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