[GRADLE-278] Automatically set version number Created: 23/Oct/08  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Martin Vlcek Assignee: Unassigned
Resolution: Won't Fix Votes: 3


 Description   

In the init-Task of the Java plugin do the following, if the project.version is not yet set:

  • get the latest version number for the current project module (project.group/project.name) from Ivy using the uploadResolver(s) from uploadLibs
  • if no published version was found, assume 0.0.0
  • if the (system) property 'major' is set, increment the major version number and set minor/patch to 0, similar for properties 'minor' and 'patch', otherwise if the current version is not a snapshot version, increment the patch number and add '-SNAPSHOT' (configurable?) to the version (this ensures that using 'latest.integration' as version in a dependency will really get the latest version)
  • set project.version to the calculated value

This should be quite easy to implement (if you know the Ivy-API) and would implement a default behavior which can easily be ignored (by setting the project.version manually).

This allows the user to use a call like the following to create a new build with the next minor version number:

  • gradle -Dminor uploadLibs
    The version number is always incremented (or stays the same for snapshots)

For the full discussion see http://www.nabble.com/Version-numbers-to20112226.html

 Comments   
Comment by Martin Vlcek [ 23/Oct/08 ]

See also Issue 277 (http://jira.codehaus.org/browse/GRADLE-277)

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 11:26:07 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.