[jira] [Commented] (MPMD-266) Aggregate report in multi-module projects doesn't use correct auxclasspath

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on MPMD-266:
-----------------------------

Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » MPMD-277 #4

See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/MPMD-277/4/

> Aggregate report in multi-module projects doesn't use correct auxclasspath
> --------------------------------------------------------------------------
>
>                 Key: MPMD-266
>                 URL: https://issues.apache.org/jira/browse/MPMD-266
>             Project: Maven PMD Plugin
>          Issue Type: Bug
>          Components: PMD
>    Affects Versions: 3.9.0
>            Reporter: Andreas Dangel
>            Assignee: Andreas Dangel
>            Priority: Major
>             Fix For: 3.11.0
>
>
> When generating a site with the pmd report enabled and using "aggregate=true", then more PMD violations are found than it should be.
>  
> The reason is probably a wrong configured auxclasspath for PMD: In aggregate mode, PMD is executed once for all modules. The classpath needs to include all dependencies of all modules, in oder for the typeresolution feature to work. Currently, only the compile classpath of the parent module is used.
>  
> Relevant code parts:
>  * Determining the auxclasspath: [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L665-L678]
>  * Determining the source folders: [https://github.com/apache/maven-pmd-plugin/blob/09f7b9a83818b5c93d8731c0a7d263128d06c6e4/src/main/java/org/apache/maven/plugins/pmd/AbstractPmdReport.java#L362-L391]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)