[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

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Using version notation below works with gradle 1.7 and 1.8, but is broken in 1.9.

repositories {
configurations {
dependencies {
config 'junit:junit:[4.10,4.+]'

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


Root project

--- junit:junit:[4.10,4.+] FAILED

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 [ 24/Jan/17 ]

I believe for version ranges you'll have to give concrete versions e.g. [4.10,4.12].

Generated at Wed Jun 30 12:36:06 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.