chore: seperate release plugins to a profile #467
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR
Attempts to improve local development experience by isolating artifact release time plugins into a dedicated profile. Profile
deploy
is activated by default, hence no change is needed in CI (GH Actions). However, the developer now can disable this profile with profile disable command<mvn command> -P -deploy
so that they do not need to worry about deploy time executions (ex:- artifact signing)How to use
For local development builds without release, signing and java docs use maven command -
mvn clean install -P -deploy