[GRADLE-1418] Tooling API should provide as much information as possible in the presence of failures Created: 04/Mar/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Won't Fix Votes: 1


For example, the failure to resolve or download a dependency should not prevent the rest of the model, such as the source directories, project dependencies or resolved dependencies, from being returned to the client.

Comment by Kris De Volder [ 11/May/11 ]

I've got another example why this is very important.

Just tried to import the spring data mapping project in STS-Gradle.

The import wizard fails because a single dependency that can not be found.
It is poor tooling that breaks down completely because of a single missing dependency problem with a project.

I can understand it is tricky to anticipate everything that may go wrong... but we now have already two examples where a missing dependency is spoiling the fun. So it would be nice to handle that case at least.

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:55:02 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.