-
Notifications
You must be signed in to change notification settings - Fork 130
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
Launch/Diff Groovy should remove use of maven-checkstyle-plugin #273
Comments
I am ok create issue on Checkstyle to generate HTML report, I think we already have such issue, and raised this in discussions several times. Html generation is better to be done html template libraries but it is new dependency .... so it is ok to generate html by old-fashioned way (StringBuilder.append)
this is plugin that we benefit a lot, to convert sources to html. It(as a tool) might be used separately to just convert folder of source to folder of html . |
For regression, we don't need this. |
this is result of maven-jxr-plugin - |
If you at look inputs to |
…heckstyle-plugin
…heckstyle-plugin
…heckstyle-plugin
…heckstyle-plugin
…heckstyle-plugin
…heckstyle-plugin
If this issue is completed, close #255 |
I still see usage of plugin in pom.xml - https://github.com/checkstyle/contribution/blob/master/checkstyle-tester/pom.xml#L59 @nmancus1 , please make summary of where we are now. |
We need to generate reports from checkstyle directly, but this issue is last on the list of improvements to checkstyle-tester. I have left a general update here. |
reminder: checkstyle do not have html reports, chekcstyle can generate xml report and diff.groovy can convert it to HTML. |
|
Issue checkstyle#273: converts diff.groovy to use Checkstyle's CLI
Issue checkstyle#273: converts diff.groovy to use Checkstyle's CLI
See https://issues.apache.org/jira/browse/MCHECKSTYLE-346 .
We need to deprecate all usage of
maven-checkstyle-plugin
so we can start implementing backward breaking changes.The groovy scripts are our heaviest scripts as we use them for all types of regression, so they should be the first ones converted.
Instead of installing checkstyle and then running
mvn site
, we should package the project into theall
jar and run the CLI checkstyle program and produce the XML violation file. This file and the sources will be what is fed intopatch-diff-report-tool
to produce the final report.We should not need to change
patch-diff-report-tool
. Using the CLI allows us to run Checkstyle on the repo directory directly instead of copying the files to another location temporarily. This will also allow us to run regression on non-Java files which is whatmaven-jxr-plugin
forced on us.The text was updated successfully, but these errors were encountered: