Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Move Checkstyle config location into property #3910

Conversation

slarse
Copy link
Collaborator

@slarse slarse commented May 5, 2021

Required to make #3907 green before merging, related to #3906

This PR moves the hard-coded Checkstyle config location into the checkstyle.config.location property (default user property for the <configLocation> element). This provides a default that can be overridden from the command line by specifying -Dcheckstyle.config.location=path/to/some/checkstyle.xml. This in turn is necessary for #3906 to be able to run with all the configuration in the pom for Checkstyle, but a different Checkstyle config.

@slarse slarse changed the title chore: Make Checkstyle config location configurable chore: Move Checkstyle config location into property May 5, 2021
@slarse slarse changed the title chore: Move Checkstyle config location into property review: chore: Move Checkstyle config location into property May 5, 2021
@monperrus monperrus changed the title review: chore: Move Checkstyle config location into property chore: Move Checkstyle config location into property May 5, 2021
@monperrus monperrus merged commit 56b4f4f into INRIA:master May 5, 2021
@monperrus
Copy link
Collaborator

Simple change, everything is green :) Thanks.

@slarse slarse deleted the issue/3906-make-checkstyle-config-configurable branch May 6, 2021 06:01
@monperrus monperrus mentioned this pull request Aug 19, 2021
woutersmeenk pushed a commit to woutersmeenk/spoon that referenced this pull request Aug 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants