[GRADLE-3007] Gradle could not resolve dependency with multiple versions declared in pom.xml Created: 24/Jan/14  Updated: 10/Feb/17  Resolved: 10/Feb/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: 0


 Description   

Compilation fails if there is a dependency that has multiple version declared. For example [1]http://repo1.maven.org/maven2/org/odl...

See

<jackson.version>[1.8,1.8.6],[1.9,1.9.7]</jackson.version>

If project depends from any child project i.e. wiquery-core dependency resolution fails:

FAILURE: Build failed with an exception.

----------------------------------------------------------------------------------------
[1] http://repo1.maven.org/maven2/org/odlabs/wiquery/wiquery-parent/1.5.7/wiquery-parent-1.5.7.pom



 Comments   
Comment by Gradle Forums [ 24/Jan/14 ]

Have you been able to verify that the problem is indeed the version notation, and not some other part of the POM?

Comment by Gradle Forums [ 24/Jan/14 ]

Well, I haven't tested it, but index 70 is right about here `/[1.8,1.8.6],[1.9,1.9.7]/`...
I could try though...

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 [ 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.

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