-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support using ${revision} as the project version #151
Comments
So you have |
As an example of what I am trying to do, see how Spring Boot stores the version of the project in the revision property here: https://github.com/spring-projects/spring-boot/blob/master/pom.xml. Rather than updating the |
@Froodulous That is clear. The question is: Do you want to change |
That would be ideal, yes. |
+1 for this issue. versions-maven-plugin and tycho-versions-plugin support this feature |
+1 In spring boot starters kind projects this feature help to manage the version correctly |
@Froodulous Steps to support
Should work. :) |
@Froodulous @lukelalo @limkinZero |
@aleksandr-m Sorry for the delay replying to this. It works great for me. Thanks a lot for the update. |
As of version 3.5, maven supports using the ${revision} placeholder as the version of your project. This is useful in a multi-module project where I want to have a consistent version between all of the modules in the project and have some dependency management for the modules' versions.
Currently this gitflow plugin does not work with this approach - it is unable to parse the version from the pom when starting a release.
I can use the maven flatten plugin to flatten the pom before starting a release. This provides the release plugin with a proper version number and it can start the release, but it is not able to update the "revision" property in the pom to match the release version.
Is there any way to update the gitflow plugin to support this approach?
The text was updated successfully, but these errors were encountered: