[GRADLE-160] transitive maven-style dependencies are only checked for against the resolver associated with the compile dependency Created: 17/Jul/08  Updated: 04/Jan/13  Resolved: 18/Jul/08

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jerod Lass Assignee: Hans Dockter
Resolution: Not A Bug Votes: 0


Example conditions :
module mycode-1.4 has a transitive dependency on module hibernate-3.0.5
mycode is in my local maven repository but not the global maven repo
hibernate's poms exist in my local maven repository but the jars do not
hibernate jars are in the global maven repo


addMavenStyleRepo('myrepo', 'http://myrepo.com/maven-repo')
compile "me:mycode:1.4"

will not be able to resolve the runtime dependency on hibernate because it will find the poms in the local maven repository but not the jars, without ever checking the global maven repository.

Comment by Hans Dockter [ 18/Jul/08 ]

This is fortunately not a bug. Your setup does not work because the hibernate pom is in your local repository. With Ivy one resolver is responsible for catching the pom and the jar. See my posting in the mailing list.

Generated at Wed Jun 30 11:23:16 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.