[GRADLE-2436] ExternalDependency.getModuleVersion returns null for unresolved dependencies Created: 14/Aug/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Reporter:||Kris De Volder||Assignee:||Unassigned|
I discovered this while trying to implement
What this needs to be able to do is take a dependency and try to resolve it in the workspace (i.e. find a maven project in the workspace mathcing the dependency).
Unfortunately, I'm not receiving the information needed to do that unless the dependency can first be resolved outside the workspace. This seems to defeat the purpose of STS-2405, since the idea is to avoid needing to publish a jar to the some maven repo in the first place.
In other words, we need information even if the dependency was not resolvable.
I gather the reason why this is now null is because it wants to return a precise version rather than a range. (Bug:
But it would be useful to be able to obtain either a range or a precise version. I.e. it should be possible to get access to both the info used to do the resolution as well as the actual resolved result.
A complete lack of information about a given dependency when it is not resolvable seems like a poor solution (at least for my particular use-case).
|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.