[GRADLE-912] If uploadArchives task fails, the user gets a non-informative NoSuchElementException Created: 19/Apr/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Tomer Cohen | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Issue Links: |
|
||||||||
| Description |
|
In case the uploadArchives task fails, the user gets a NoSuchElementException which does not provide any information as to why the task failed, whether it be credentials, or if deploying to a wrong repository which knows how to handle only snapshots, etc... only with a -d you can see the root exception but it is quite verbose, would be nice to see it in the failure, either the exception itself, or a message describing it. |
| Comments |
| Comment by Daz DeBoer [ 28/Nov/12 ] |
|
These issues have the same symptom: could be related. |
| 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:
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. |