[GRADLE-3342] Non-versioned maven dependencies causing continuous remote resolution. Created: 24/Sep/15 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Reporter:||Adrian Kelly (Inactive)||Assignee:||Unassigned|
A dependency defined without a version number causes gradle to always attempt remote resolution (at least for maven repos) to find that dependency even though it will never find it. e.g.
It never finds the dependency because the URL to the remote repo is incorrect or perhaps there is no correct remote maven repo url for non-versioned artifacts. e.g.
Originally discovered via this post:
Reproducable with gradle 2.5 and above with: https://gist.github.com/adrianbk/1c5c2a19d7904324569d
|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.