[GRADLE-3224] Maven plugin POM generation fails to translate "+" version selector into actual version Created: 16/Jan/15  Updated: 23/Jan/17  Resolved: 23/Jan/17

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

Type: Bug
Reporter: Benjamin Muschko Assignee: Unassigned
Resolution: Duplicate Votes: 3


 Description   

Manually created from Gradle Forum post.

For the given build script:

apply plugin: 'java'
apply plugin: 'maven'

repositories {
    jcenter()
}

dependencies {
    compile 'commons-io:commons-io:+'
}

The generated POM file still uses the "+" version selector:

<dependency>
    <groupId>commons-io</groupId>
    <artifactId>commons-io</artifactId>
    <version>+</version>
    <scope>compile</scope>
</dependency>


 Comments   
Comment by Davor Sauer [ 31/Mar/16 ]

Maybe one of possible solutions will be to have property on maven-publish plugin which will resolve fixed version during publishing.

Example:

publishing {
    publications {
        maven(MavenPublication) {
            groupId 'org.gradle.sample'
            artifactId 'project1-sample'
            version '1.1'
            dependencyVersion 'fixed'

            from components.java
        }
    }
}

then upper example will have (latest resolved version in time of publication)

<dependency>
    <groupId>commons-io</groupId>
    <artifactId>commons-io</artifactId>
    <version>1.0.0</version>
    <scope>compile</scope>
</dependency>
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 John R Scancella [ 18/Nov/16 ]

This is very much an issue for me. Currently I like to use the latest version of my dependencies by using 

latest.integration

but that creates a pom like this https://oss.sonatype.org/content/repositories/snapshots/gov/loc/bagit/5.0.0-Nov-17-2016_14-47-42-SNAPSHOT/bagit-5.0.0-Nov-17-2016_14-47-42-20161117.194749-1.pom

ideally I would like it to put whatever version it resolved in the dependencies instead. Sort of related it should also NOT be using test dependencies.

Comment by Benjamin Muschko [ 23/Jan/17 ]

Work now tracked here: https://github.com/gradle/gradle/issues/1232

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