|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
A little late to the party...I was thinking of using your plugin to replace a perl scripted process that injected version numbers via expect, but without the ability to accept defaults, I can't automate a release of a pipeline of 80 artifacts.
I agree that a reactor project with varying versions in sub-modules is odd, but that shouldn't mean the whole accept default use-case is removed. Should it? I agree with jason c, this is a MAJOR feature. Did all the users of this feature simply not upgrade and are using version 0.7.1 ?