[GRADLE-1599] Project transitive dependency resolution appears not to use repositories definition from dependent project Created: 08/Jun/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
Reporter: Alan Krueger Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Issue Links:
Duplicated by GRADLE-698 Automatically add the repository loca... Resolved


One of our subprojects has a compile dependency that has a special repositories declaration so it can locate the repository and download the dependency correctly. When projects that depend on that subproject try to resolve their transitive dependencies, they appear not to see that repositories declaration and fail to resolve the dependency.

Comment by Alan Krueger [ 08/Jun/11 ]

This appears to be due to evaluating the manifest 'Class-Path' using configurations.runtime.collect at configuration time rather than runtime, as described here: http://markmail.org/message/jmvsebu6ymurd7ve

Rather than just breaking the output of the dependencies, that appears to have destructive side-effects. (For instance, calling collections.compile.collect there actually broke the compilation step.)

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

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