[ 
https://jira.codehaus.org/browse/MPMD-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315823#comment-315823
 ] 

Dennis Lundberg commented on MPMD-80:
-------------------------------------

Since the next version of the plugin will be 3.0, I suggest that we break 
backwards compatibility now. Let us add a configuration called 
"includePmdXmlInSite" that defaults to false. This means that people who want 
the pmd.xml file to be included in the site will have to configure that, when 
they upgrade the plugin to 3.0. I think that most people don't care if the 
pmd.xml file is included in the site or not. It's better that our plugins are 
consistent in their behavior.
                
> maven-pmd-plugin should generate only one pmd.xml file
> ------------------------------------------------------
>
>                 Key: MPMD-80
>                 URL: https://jira.codehaus.org/browse/MPMD-80
>             Project: Maven 2.x PMD Plugin
>          Issue Type: Improvement
>          Components: PMD
>    Affects Versions: 2.3
>            Reporter: Ulli Hafner
>            Priority: Minor
>
> Currently the task mvn pmd:pmd generates two identical pmd.xml report files: 
> one file is in target/pmd.xml, the other in target/site/pmd.xml. (findbugs 
> and checkstyle just generate one file in the target folder).
> These two identical files hinder the processing by warning visualizations 
> tools (like the Hudson CI server pmd-plugin) that use these m2 generated 
> files as input. Normally, in Hudson one can just specify the file pattern 
> **/pmd.xml to obtain the available files to process. (Of course the user 
> might change the default pattern to **/target/pmd.xml, but it would be much 
> smarter if this would not be a requirement. And using **/target/pmd.xml as 
> default is also no possibility, since ant has no target folder...)
> See: https://hudson.dev.java.net/issues/show_bug.cgi?id=1647

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to