docs: Document outputDirectory and other configuration parameters #72
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.
Summary
This PR documents three configuration parameters that already exist in the plugin code but were not documented in the README:
outputDirectory- Control where.ci-friendly-pom.xmlis writtenciFriendlyPomFilename- Customize the flattened POM filenameautoRewriteCiFriendlyPoms- Skip rewrites when POM is up-to-dateMotivation
While investigating how to keep
.ci-friendly-pom.xmlfiles out of the workspace root in multi-module projects, I discovered that theoutputDirectoryparameter already exists inAbstractCiFriendlyMojobut is not documented.This makes it difficult for users to discover this useful feature.
Changes
outputDirectorywith example showing${project.build.directory}usage.gitignoreentries, consistency with Maven practicesciFriendlyPomFilenamewith both POM and command-line examplesautoRewriteCiFriendlyPomsfor build optimizationTesting
I've tested the
outputDirectoryconfiguration in a multi-module project and confirmed:<outputDirectory>${project.build.directory}</outputDirectory>successfully writes.ci-friendly-pom.xmlto thetarget/directory.ci-friendly-pom.xmlfiles clutter the workspaceExample Usage
Related
These parameters have existed since the plugin's initial implementation but were not included in the README documentation.