[GRADLE-2410] configuration resolves fine even though some transitive dependencies are unresolvable Created: 01/Aug/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 0


1. Let's assume foo->bar dependency is incorrectly declared in foo's ivy file (for example configuration is incorrect). This means that 'foo' module is not resolvable on its own and root resolution fails:


2. However, if 'bar' is resolved somewhere else in the graph then the root's resolution fail

root->foo->bar - root resolution fails

However we approach this problem we must consider backwards compatibility.

Comment by Szczepan Faber [ 01/Aug/12 ]

A different (see Adam's comment below) but somewhat similar issue is: GRADLE-2433

Comment by Adam Murdoch [ 06/Aug/12 ]

Can you add a separate issue for the second problem? They'll need to be fixed separately.

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 12:21:09 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.