You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let me start with what I'm trying to achieve. I have a multi-module build and I want it to fail on a violation, quickly.
I'm not interesting in producing a report.
The build may include anything from a single module to all modules. In each case, I don't want PMD to try parse the entire code base if I only asked Maven to build a single module.
I notice that if I use the "aggregate-pmd-check" goal, I get log lines like [WARNING] org.apache.maven.plugins.pmd.AggregatorPmdReport - Unable to locate Source XRef to link to - DISABLED
Why is AggregatorPmdReport being invoked? Sounds like a legacy issue.
I also notice that unlike most Maven plugins, the pmd-maven-plugin goal is always forking, indicated by chevrons in the output <<< pmd:3.22.0:check
With a single custom XPath rule, the time to complete a build becomes impractical.
I was hoping to add pmd to my list of static analysis checkers/formatters like checkstyle, impsort, sortpom, errorprone, modernizer etc which are all able to parse source code and do various checks without becoming a burden.
With the current state of the pmd-maven-plugin (v3.22.0) that does not look likely.
The text was updated successfully, but these errors were encountered:
Let me start with what I'm trying to achieve. I have a multi-module build and I want it to fail on a violation, quickly.
I'm not interesting in producing a report.
The build may include anything from a single module to all modules. In each case, I don't want PMD to try parse the entire code base if I only asked Maven to build a single module.
I notice that if I use the "aggregate-pmd-check" goal, I get log lines like
[WARNING] org.apache.maven.plugins.pmd.AggregatorPmdReport - Unable to locate Source XRef to link to - DISABLED
Why is AggregatorPmdReport being invoked? Sounds like a legacy issue.
I also notice that unlike most Maven plugins, the pmd-maven-plugin goal is always forking, indicated by chevrons in the output
<<< pmd:3.22.0:check
With a single custom XPath rule, the time to complete a build becomes impractical.
I was hoping to add pmd to my list of static analysis checkers/formatters like checkstyle, impsort, sortpom, errorprone, modernizer etc which are all able to parse source code and do various checks without becoming a burden.
With the current state of the pmd-maven-plugin (v3.22.0) that does not look likely.
The text was updated successfully, but these errors were encountered: