Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <9512095.1237396992947.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Wed, 18 Mar 2009 12:23:12 -0500 (CDT)
From: "Carlos Sanchez (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Closed: (MAVENUPLOAD-2387) Transitive dependencies in
 eclipse jdt core are broken
In-Reply-To: 
 <20337012.1236587352966.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ http://jira.codehaus.org/browse/MAVENUPLOAD-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlos Sanchez closed MAVENUPLOAD-2387.
---------------------------------------

      Assignee: Carlos Sanchez
    Resolution: Won't Fix

There are many issues with version ranges and osgi, but that's more of a Maven issue than repository problem
Please refer to the mailing list for questions

> Transitive dependencies in eclipse jdt core are broken
> ------------------------------------------------------
>
>                 Key: MAVENUPLOAD-2387
>                 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2387
>             Project: Maven Upload Requests
>          Issue Type: Bug
>            Reporter: Dave Syer
>            Assignee: Carlos Sanchez
>
> Transitive dependencies in eclipse jdt core are broken.  I can MAVENUPLOAD-1795 that the JDT core JAR was uploaded (the version number does not match the actual one in the repo, so maybe that is part of the problem - the repo has 3.3.0-v_771).  This JAR has dependencies and transitive dependencies that (quite sensibly) use version ranges.  But the ranges do not match any deployed versions of the dependencies, so if you try to use it you get, for example
> Caused by: org.apache.maven.artifact.versioning.OverConstrainedVersionException: Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
>   org.eclipse.equinox:app:jar:null
> There seems to be an issue with the form of the version in the app artifact.  It looks like it might match, but clearly doesn't.

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