[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
Manually created from Gradle Forum post.
For the given build script:
The generated POM file still uses the "+" version selector:
|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.
then upper example will have (latest resolved version in time of publication)
|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:
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
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