[GRADLE-2961] Dynamic version ranges broken (or at least, different) in Gradle 1.9 Created: 25/Nov/13 Updated: 24/Jan/17 Resolved: 24/Jan/17
Using version notation below works with gradle 1.7 and 1.8, but is broken in 1.9.
I looked at the release notes and did not find any reason for this to have broken. Is there a better way to approach this functionality?
|Comment by Gradle Forums [ 25/Nov/13 ]|
Also, I guess I never specified. When running 'gradle dependencies' with 1.9 the output is
|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 [ 24/Jan/17 ]|
I believe for version ranges you'll have to give concrete versions e.g. [4.10,4.12].