[
https://jira.codehaus.org/browse/MRELEASE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305952#comment-305952
]
Michael Wenig commented on MRELEASE-473:
----------------------------------------
Hi Sergio,
we did workaround this problem. We have an application which is using the
release plugin and decides which version (and set them manually) - not really
nice but it is working. For now this app has been growing and therefore now
also the right place to decide this (e.g. there are some automatism to
reconfiguring jenkins jobs etc.)
But of course - the plugin should work in a usable way....
Regards Michael
> when branching the minor-version-number should be increased not the
> incremental version
> ---------------------------------------------------------------------------------------
>
> Key: MRELEASE-473
> URL: https://jira.codehaus.org/browse/MRELEASE-473
> Project: Maven 2.x Release Plugin
> Issue Type: Wish
> Components: branch
> Affects Versions: 2.0-beta-9
> Reporter: Michael Wenig
>
> When you are using the branches the follwowing method is normally used (at
> least at the sites I am working):
> trunk:
> major.minor.1-SNAPSHOT
> releases are only made out of a branch, so the branch name is normally
> Release_major_minor and the incremental number denotes the release.
> Now a problem occurs in the trunk as per default just the incremental version
> is increased (as -SNAPSHOT)
> Example:
> Version on trunk: 0.0.1-SNAPSHOT
> create a branch Release_0_0
> Now on branch there is 0.0.1-SNAPSHOT (correct)
> On trunk is 0.0.2-SNAPSHOT per default which will conflict when doing a
> release on the branch (as there will be also a 0.0.2-SNAPSHOT per default)
> On trunk it would make more sense to have either 0.1.0-SNAPSHOT oder
> 1.0.0-SNAPSHOT
> So the normal case is to have someone decide on branching if the major or
> minor-version should be increased on the trunk. Currently everytime someone
> has to manually redefine the new development version. Increasing the
> minor-number and resetting the incremental to '0' would be a more useful
> default as it is the way 99% of the numbers are made.
> Another way I saw is to have on trunk only 2-numbered-versions (as
> 0.1-SNAPSHOT) and then directly after branching changing the version on the
> branch to 0.1.0-SNAPSHOT. This also makes sense especially if you only want
> to branch if you have to make some hotfixes.
> I would suggest to add a parameter to the branch goal which is able to switch
> between the three possibilities:
> - the 'old way' (even if from my sight the current scheme could be
> completely dropped as I do not know any project which is able to use this)
> - increasing the minor number on trunk and resetting the incremental to
> 0-SNAPSHOT
> - using two-number-scheme on trunk and three number-scheme on branch
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
