Drop the sec-dispatcher gap and document the site workflow - #63
Merged
Conversation
plexus-sec-dispatcher now has the scm-publish binding every other single-module project uses, so the documented command works there too. Removes the 'Known gap' section. Replaces 'why this isn't automated' with how to use the Publish Site workflow, and keeps the reasoning for why it is triggered by hand rather than on release. Follow-up to codehaus-plexus/plexus-sec-dispatcher#133 and #62.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Part of #58. Two small corrections to
RELEASING.md, both now out of date.The "Known gap" section goes. It said
plexus-sec-dispatcherhas nomaven-scm-publish-pluginconfiguration so neither documented command works there. That was true when I wrote it; codehaus-plexus/plexus-sec-dispatcher#133 has since added the same binding every other single-module project uses, and it is merged."Why this isn't automated" becomes "how to use it". It said a
workflow_dispatchworkflow "is the intended next step". That is #62. The section now tells a release manager how to run it — including thatdry-runis worth using the first time on any given project — and keeps the reasoning for why it is hand-triggered rather than release-triggered, since that is a deliberate choice someone will eventually want to revisit.Depends on #62 for the second half to be accurate, so merge that first.