[GRADLE-3529] Gradle compares versions differently to maven Created: 19/Aug/16  Updated: 20/Jan/17  Resolved: 20/Jan/17

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

Type: Bug
Reporter: Stefan Wolf Assignee: Unassigned
Resolution: Duplicate Votes: 0


 Description   

See https://discuss.gradle.org/t/cannot-resolve-dependencies-that-are-resolved-by-maven/18894

Given version range for dependencies Maven sometimes finds a matching dependency, whereas Gradle doesn't. This was reported to happen for the following build script:

apply plugin: 'java'

repositories {
    mavenCentral()
}

dependencies {
    compile group: 'org.eclipse.scout.sdk.deps', name: 'org.eclipse.jface', version: '3.12.0.v20160518-1929'
}

Error:

Could not find any version that matches org.eclipse.scout.sdk.deps:org.eclipse.swt.win32.win32.x86:[3.105.0,3.105.1).
  Versions that do not match:
      3.105.0.v20160603-0902
      3.104.0.v20150528-0211

The StaticVersionComparator compares the various parts of two versions. Given that one version (like 3.8.0.v) has a part which another version doesn't (the v compared to 3.8.0) the version is bigger if the part is a number and smaller if the part is something else. This means that 3.8.0.v (or 3.8.0.v20160316-1921) is smaller than 3.8.0 since v is not a number (see the code2).
Maven uses a different kind of strategy to compare versions.

 Comments   
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 Stefan Wolf [ 20/Jan/17 ]

I am closing this as duplicate of https://github.com/gradle/gradle/issues/1218.

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