You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Dangel (Jira)" <ji...@apache.org> on 2021/09/05 18:28:00 UTC

[jira] [Commented] (MPMD-283) Create a real aggregate goal

    [ https://issues.apache.org/jira/browse/MPMD-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410233#comment-17410233 ] 

Andreas Dangel commented on MPMD-283:
-------------------------------------

Fixed in https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=commit;h=5ae53f135b46102e7b749c834173cdc97678f834

> Create a real aggregate goal
> ----------------------------
>
>                 Key: MPMD-283
>                 URL: https://issues.apache.org/jira/browse/MPMD-283
>             Project: Maven PMD Plugin
>          Issue Type: Task
>          Components: CPD, PMD
>            Reporter: Andreas Dangel
>            Priority: Major
>             Fix For: 3.15.0
>
>
> PMD needs to have the project compiled, before it can analyze it. This is required to support typeresolution.
> For Multi-modules projects, you can currently set the "aggregate" parameter, to create an aggregated report. However, this is executed at the root project _before_ all other modules have been built, leading to a potentially inaccurate PMD result and false positives.
> A separate goal should be introduced, that can execute the compile lifecycle prior to executing PMD (similar what javadoc:aggregate does).
>  
> {code:java}
> @Mojo( name = "aggregate", aggregator = true, requiresDependencyResolution = ResolutionScope.TEST )
> @Execute( phase = LifecyclePhase.COMPILE )
> public class AggregatorPMDReport {
> ...{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)