You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robin Vobruba (JIRA)" <ji...@codehaus.org> on 2012/02/09 22:57:03 UTC
[jira] (MPMD-143) module site(s) created in the wrong place
Robin Vobruba created MPMD-143:
----------------------------------
Summary: module site(s) created in the wrong place
Key: MPMD-143
URL: https://jira.codehaus.org/browse/MPMD-143
Project: Maven 2.x PMD Plugin
Issue Type: Bug
Components: CPD, PMD
Affects Versions: 2.7, 2.6
Environment: Linux, Maven 2.2.1
Reporter: Robin Vobruba
Attachments: TestProject.zip
having this project structure:
pom.xml[type=pom, defines the pmd plugin in the reporting section]
modules/part1/pom.xml[type=jar]
modules/part2/pom.xml[type=jar]
running "mvn site" on the parent project generates all reports on the parent target/site/ folder (Project License, CheckStyle, FindBugs, ...), except PMD and CPD, which get generated in the two modules target/site/ dirs, and thus do not show up in the main report.
tested with maven PMD plugin versions 2.6 and 2.7.
if more info is needed, or testing, tell me please.
i attached a a zip file with a quite minimal test project.
The zip contains a folder TestProject with the above structure inside. try running "mvn site" in folder TestProject, and have a loot at:
target/site/
modules/part1/target/site/
modules/part2/target/site/
--
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
[jira] (MPMD-143) module site(s) created in the wrong place
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPMD-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291357#comment-291357 ]
Dennis Lundberg commented on MPMD-143:
--------------------------------------
This is the expected behavior. The PMD Plugin by default does *not* create an aggregated report for a multi-module build. You need to configure that yourself, by setting the "aggregate" parameter to true.
http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#aggregate
> module site(s) created in the wrong place
> -----------------------------------------
>
> Key: MPMD-143
> URL: https://jira.codehaus.org/browse/MPMD-143
> Project: Maven 2.x PMD Plugin
> Issue Type: Bug
> Components: CPD, PMD
> Affects Versions: 2.6, 2.7
> Environment: Linux, Maven 2.2.1
> Reporter: Robin Vobruba
> Attachments: TestProject.zip
>
>
> having this project structure:
> pom.xml[type=pom, defines the pmd plugin in the reporting section]
> modules/part1/pom.xml[type=jar]
> modules/part2/pom.xml[type=jar]
> running "mvn site" on the parent project generates all reports on the parent target/site/ folder (Project License, CheckStyle, FindBugs, ...), except PMD and CPD, which get generated in the two modules target/site/ dirs, and thus do not show up in the main report.
> tested with maven PMD plugin versions 2.6 and 2.7.
> if more info is needed, or testing, tell me please.
> i attached a a zip file with a quite minimal test project.
> The zip contains a folder TestProject with the above structure inside. try running "mvn site" in folder TestProject, and have a loot at:
> target/site/
> modules/part1/target/site/
> modules/part2/target/site/
--
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
[jira] (MPMD-143) module site(s) created in the wrong place
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPMD-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MPMD-143.
--------------------------------
Resolution: Not A Bug
Plugins handle aggregated reports differently. The old way, which maven-pmd-plugin uses, has an aggregate parameter. The new way has two different reports - one aggregated and one non-aggregated. Hopefully we can converge all plugins so that they all work in the same way, but that will take some time...
> module site(s) created in the wrong place
> -----------------------------------------
>
> Key: MPMD-143
> URL: https://jira.codehaus.org/browse/MPMD-143
> Project: Maven 2.x PMD Plugin
> Issue Type: Bug
> Components: CPD, PMD
> Affects Versions: 2.6, 2.7
> Environment: Linux, Maven 2.2.1
> Reporter: Robin Vobruba
> Attachments: TestProject.zip
>
>
> having this project structure:
> pom.xml[type=pom, defines the pmd plugin in the reporting section]
> modules/part1/pom.xml[type=jar]
> modules/part2/pom.xml[type=jar]
> running "mvn site" on the parent project generates all reports on the parent target/site/ folder (Project License, CheckStyle, FindBugs, ...), except PMD and CPD, which get generated in the two modules target/site/ dirs, and thus do not show up in the main report.
> tested with maven PMD plugin versions 2.6 and 2.7.
> if more info is needed, or testing, tell me please.
> i attached a a zip file with a quite minimal test project.
> The zip contains a folder TestProject with the above structure inside. try running "mvn site" in folder TestProject, and have a loot at:
> target/site/
> modules/part1/target/site/
> modules/part2/target/site/
--
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
[jira] (MPMD-143) module site(s) created in the wrong place
Posted by "Robin Vobruba (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPMD-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292086#comment-292086 ]
Robin Vobruba commented on MPMD-143:
------------------------------------
i see, thanks!
but... if all other plugins do aggregate (by default, or always), why does the PMD plugin not do this too? it is quite unintuitive and .. the way i currently see it, also a wrong/bad choice. i'd be glad to be enlightend though, if there is a good reason for it.
> module site(s) created in the wrong place
> -----------------------------------------
>
> Key: MPMD-143
> URL: https://jira.codehaus.org/browse/MPMD-143
> Project: Maven 2.x PMD Plugin
> Issue Type: Bug
> Components: CPD, PMD
> Affects Versions: 2.6, 2.7
> Environment: Linux, Maven 2.2.1
> Reporter: Robin Vobruba
> Attachments: TestProject.zip
>
>
> having this project structure:
> pom.xml[type=pom, defines the pmd plugin in the reporting section]
> modules/part1/pom.xml[type=jar]
> modules/part2/pom.xml[type=jar]
> running "mvn site" on the parent project generates all reports on the parent target/site/ folder (Project License, CheckStyle, FindBugs, ...), except PMD and CPD, which get generated in the two modules target/site/ dirs, and thus do not show up in the main report.
> tested with maven PMD plugin versions 2.6 and 2.7.
> if more info is needed, or testing, tell me please.
> i attached a a zip file with a quite minimal test project.
> The zip contains a folder TestProject with the above structure inside. try running "mvn site" in folder TestProject, and have a loot at:
> target/site/
> modules/part1/target/site/
> modules/part2/target/site/
--
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