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

checkstyle-tester: disable launch.groovy's site during diff.groovy and do checkstyle alone #367

Closed
rnveach opened this issue Apr 8, 2019 · 2 comments

Comments

@rnveach
Copy link
Member

rnveach commented Apr 8, 2019

When launch.groovy is done it's execution, it goes through the site directory and removes non-referenced files in the generated site that don't show up in the checkstyle xml results, and some other misc stuff.
https://github.com/checkstyle/contribution/blob/master/checkstyle-tester/launch.groovy#L239

However, when diff.groovy is the one executing launch.groovy it doesn't use this resulting site build and actually builds it's own version instead during the call to patch-diff-report-tool. All we save from the original run of launch.groovy is the resulting XML file.
https://github.com/checkstyle/contribution/blob/master/checkstyle-tester/diff.groovy#L223

This is what makes Issue #273 possible as pure checkstyle can generate its own XML file and we don't need maven at all. This issue assumes #273 isn't done yet. If it does get done, this issue can be closed.

We should create a new option to send to launch.groovy to disable the site build and everything related to it but only run maven-checkstyle. This will save time by not doing something that isn't even needed.

@rnveach
Copy link
Member Author

rnveach commented Dec 29, 2022

@rnveach
Copy link
Member Author

rnveach commented Dec 29, 2022

Comparing

def postProcessCheckstyleReport(targetDir) {

to https://github.com/checkstyle/contribution/blob/master/checkstyle-tester/diff.groovy#L650

It looks like this is done already. We don't deal with the site directory anymore and fully rely on patch-diff-report-tool to generate all our HTML needs. postProcessCheckstyleReport was copied in at 80943b7 and it never included the site directory stuff.

I feel we can close this issue as basically done.

@rnveach rnveach closed this as completed Dec 29, 2022
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

No branches or pull requests

1 participant