[GRADLE-3036] certain resolve exceptions may be lost during the resolution Created: 04/Mar/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


 Description    
dependencies {
  compile "org:foo:1.0" { transitive = false }
  compile "org:bar:1.0"
}
//graph:  foo:1.0 -> bar:1.0 -> missing:1.0

The error message will say that missing:1.0 cannot be resolved and is pulled by direct dependency foo:1.0. Normally, it's ok, however in this instance the direct dependency foo:1.0 is declared as transitive = false. So the exception message should say that missing:1.0 is not found but it is pulled by bar->foo->missing. In real life, when there are lots of dependencies, it's quite hard to track the problem.

My theory is that we're missing the right exception for some reason somewhere in the code that consumes the resolve results and serializes them to disk.

 Comments   
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:38:10 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.