[
https://issues.jenkins-ci.org/browse/JENKINS-11466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158791#comment-158791
]
Allen Lau commented on JENKINS-11466:
-------------------------------------
I rely on it for releasing patched binaries.
So each module usually have a different version number than the
parent/aggregate pom that the jenkins job is triggering.
> reenable "ability to let maven decide the versioning"
> -----------------------------------------------------
>
> Key: JENKINS-11466
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11466
> Project: Jenkins
> Issue Type: Improvement
> Components: m2release
> Reporter: domi
> Assignee: teilo
>
> It kind of feels odd to remove a useful feature just because the information
> is used for a tooltip in the UI.
> please reenable the option "let maven decide the versioning"" removed in 0.8.0
> without this option one is not able to have a workaround to define different
> versions for each module.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
