Mavin-plugin pom generator doesn't handle map gradle dynamic dependency correctly to maven dynamic dependency

Old Forum Archive
1

For gradle dependencies like this: compile group: ‘org.slf4j’, name: ‘slf4j-simple’, version: ‘1.7.+’

the maven plugin maps it to:

org.slf4j

slf4j-api

1.7.+

compile

But the contents of the version tag should look like this:

[1.7,)

See http://www.maestrodev.com/better-builds-with-maven/creating-applications-with-maven/resolving-dependency-conflicts-and-using-version-ranges/

The code here:

https://github.com/spring-projects/spring-build-gradle/blob/master/maven-deployment.gradle seems to copy the version info verbatim w/o checking for this case:

https://github.com/spring-projects/spring-build-gradle/blob/master/maven-deployment.gradle

2

Gradle doesn’t do any mapping for version range syntax, but I believe that ‘1.7.+’ is also supported by Maven. Have you tried using ‘[1.7,)’ in the build script?

3

You mean in the build.gradle script? That’s the wrong syntax for gradle AFAIK.

If you try adding a maven dependency on the pom that’s generate, you get this error:

Could not find artifact org.slf4j:slf4j-api:jar:1.7.+ in central (http://repo1.maven.org/maven2/) so that appears to be the wrong syntax. That’s why I linked this which describes the different syntaxes for their dynamic dependencies:

http://www.maestrodev.com/better-builds-with-maven/creating-applications-with-maven/resolving-dependency-conflicts-and-using-version-ranges/

I’m trying to work around it by doing something like this but haven’t gotten it working yet:

pom.whenConfigured { generatedPom ->

generatedPom.dependencies.each { mavenDep ->

if (isDynamic(mavenDep)) {

println(‘processing’ + mavenDep)

mavenDep.version = ‘[’ + mavenDep.version.replaceAll(’+’,’,’) + ‘)’

}

}

}

4

ok…this seems to work ‘’’’ pom.whenConfigured { generatedPom ->

generatedPom.dependencies.each { mavenDep ->

if (isDynamic(mavenDep)) {

mavenDep.version = ‘[’ + mavenDep.version[0…-2] + ‘,)’

}

}

} boolean isDynamic(def dep) {

return dep.version.any { it == ‘[’ || it == ‘]’ || it == ‘(’ || it == ‘)’ || it == ‘+’ } } ‘’’’

5

This works fine for me:

dependencies {
    compile "org.slf4j:slf4j-api:[1.7,)"
}

PS: Please use HTML code tags for code snippets.

6

Thanks, Peter. Is this an officially support dynamic version syntax? The Gradle manual seems to specify the + syntax here and has no mention you can use the Maven syntax:

http://www.gradle.org/docs/current/userguide/dependency_management.html

7

Gradle supports the same syntax as Ivy, which supports the Maven syntax. So I’d say it’s supported.

8

Thanks, Peter. Could you guys update the Gradle docs to include examples of this? Most people probably don’t know about it. I don’t think I’ve ever seen this syntax in any open source projects I’ve looked at…

9

Best way to get this fixed is to send a pull request.

10

This has since been fixed and will be released in Gradle 2.3. It will also be enforced for deployments to the Central Repository to avoid incompatibilities.

http://central.sonatype.org/articles/2014/Nov/28/enforcing-valid-dependency-versions/