Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0.0
-
None
Description
Not sure why resolving dependencies is needed for running Checkstyle, it does slow down the build considerably. For Apache Camel this makes a ten fold difference from ~20mins to ~2mins for running mvn checkstyle:check.
Seems this was introduced with MCHECKSTYLE-163 but subsequently integration test was removed in MCHECKSTYLE-272.
I've created a GitHub pull request to address this:
https://github.com/apache/maven-checkstyle-plugin/pull/5
Attachments
Issue Links
- causes
-
MCHECKSTYLE-377 Violations or exceptions when using "external" FQCNs in @throws after upgrade to 3.1.0
- Closed
- relates to
-
MCHECKSTYLE-166 Drop @requiresDependencyResolution test
- Closed
- links to