This repository has been archived by the owner on Dec 23, 2023. It is now read-only.
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.
The readme for https://github.com/mathieucarbou/license-maven-plugin is getting a little unwieldy, and was about to add to its length. We discussed briefly having these as normal maven sites (for plugins it's handy because you get the maven-plugin-plugin generated parameter documentation from the javadocs above the Parameters).
Here's an example of what this looks like: https://rremer.github.io/parent-pom/scm.html
I obviously deployed with alternate parameters so I could show it off, this was my deploy command:
The important bit here is that downstream projects should have to configure anything at all, so if we want to update the parent (post release) in license-maven-plugin, you just do a
mvn site site-deploy
.