[GitHub] [maven-mvnd] aalmiray edited a comment on pull request #574: Refactor build and release workflows

[GitBox <gi...@apache.org>]

aalmiray edited a comment on pull request #574:
URL: https://github.com/apache/maven-mvnd/pull/574#issuecomment-1009806534


   Got it. But you do raise a point with moving the version to the next available number and publishing artifacts to Maven Central.
   
   Version bump can happen with the `versions` plugin in which case you must set the number. Same goes by setting next snapshot. At least 2 different invocations of mvn. The `release` plugin does this for  you in 1 invocation (assuming build success).
   
   If mvnd does not deploy artifacts to Maven Central then the release plugin may still be used for handling the numbering scheme while disabling the deploy phase so that no artifacts are pushed to MC, isn't that the case?
   
   So we have a few options:
   
   - use the maven release plugin. it'll set the version to release, tag, bump version to next. the tag triggers the release-candidate workflow which only creates the git release with changelog. 
   
   - use manual steps with versions plugin to set the version. JReleaser tags and creates git release with changelog. you may or may not bump the version to next, again using the versions plugin.
   
   Both options may be triggered from GH actions, matter of fact I'd say it's a must for option 2. 
   
   Option 1. can still be triggered locally by the release master as the release-candidate workflow would have a tag trigger that does not care if the tag was made locally or on CI. 


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org