Jesse, All, Thanks for that. I did notice this discrepancy when looking into this further. I should have updated my email more promptly. I have managed to release, but I think I am running into a known issue: https://issues.apache.org/jira/browse/SCM-740
As it stands I now have a successful release but the naming is 1.01-SNAPSHOT, despite my POM initially reading this and my input to the release plugin accepting the defaults, e.g. "1.01," next version for dev.suggested "1.02-SNAPSHOT" and so on. I have tried the fixes, but now since my desired release tag exists I am stuck. Before I continue to iterate releases, perhaps in error, to have my release version not include -SNAPSHOT, would you have any advice on this scenario? Regards, Ryan Black On Wednesday, February 24, 2016 at 12:33:17 PM UTC-6, Jesse Glick wrote: > > The version in the POM should always be a snapshot, e.g., `1.1-SNAPSHOT`, > except during tagged release commits made by `mvn release: prepare > release:perform`. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1f0312fb-ec1b-4f14-a297-912587f36841%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
