gnodet commented on pull request #574: URL: https://github.com/apache/maven-mvnd/pull/574#issuecomment-1009787556
> Right. If the maven release plugin is used then a tag and a new version will be already set. The release-candidate workflow would have to be changed to be triggered on tag creation and keep JReleaser from creating a tag (as it's already there). > > If the release-candidate workflow were the starting point then you'd have to change version from snapshot to release (in all poms), let JReleaser create the tag (or explicit tag in the workflow), issue a deploy to Maven Central (not using the release plugin), and to be honest it already sounds complicated, at least to me. > > Starting the release process with the maven release plugin, having the release-candidate be triggered on tag creation sounds better to me from a minimalistic automation POV, less moving parts IMHO. Sorry if I've been misunderstood. I did not imply we should keep the maven release process, but I was only describing the _usual_ release process for simple maven based projects. So a manual trigger can be used as the starting point and have jreleaser create the tag itself as part of its release process. We just need to be able to vote on the packages (so they need to be built and staged) before being published. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
