[
http://jira.codehaus.org/browse/MCOBERTURA-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264348#action_264348
]
Mirko Friedenhagen edited comment on MCOBERTURA-145 at 4/21/11 4:42 PM:
------------------------------------------------------------------------
Yes, I am claiming this. If you check out the test project and invoke "mvn
clean install site", the cobertura reports are created in the modules with
tests. Now only changing the version of the plugin from 2.4 to 2.5 will always
skip the creation of cobertura reports at all, the output for 2.5 looks like
this:
{code}
[INFO] <<< cobertura-maven-plugin:2.5:cobertura (report:cobertura) @ app1 <<<
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[INFO] Skipped "Cobertura Test Coverage" report, file "index.html" already
exists for the English version.
[INFO] Generating "Continuous Integration" report ---
maven-project-info-reports-plugin:2.3.1
{code}
while for 2.4 it looks like this:
{code}
[INFO] Generating "Cobertura Test Coverage" report ---
cobertura-maven-plugin:2.4
[INFO] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
Cobertura: Loaded information on 1 classes.
Report time: 182ms
[INFO] Cobertura Report generation was successful.
{code}
With 2.4, when going into {{MODULE/target/site}}, there exists a directory
called {{cobertura}} and
{{project-reports.html}} in the directory has a link pointing to
{{cobertura/index.html}}.
With 2.5, when going into {{MODULE/target/site}}, there does not exist a
directory called {{cobertura}} and
{{project-reports.html}} in the directory has a link pointing to {{index.html}}.
I will attach the complete console output for 2.4 and 2.5.
was (Author: mfriedenhagen):
Yes, I am claiming this. If you check out the test project and invoke "mvn
clean install site", the cobertura reports are created in the modules with
tests. Now only changing the version of the plugin from 2.4 to 2.5 will always
skip the creation of cobertura reports at all, the output looks like this:
{code}
[INFO] <<< cobertura-maven-plugin:2.5:cobertura (report:cobertura) @ app1 <<<
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[INFO] Skipped "Cobertura Test Coverage" report, file "index.html" already
exists for the English version.
[INFO] Generating "Continuous Integration" report ---
maven-project-info-reports-plugin:2.3.1
{code}
With 2.4, when going into {{MODULE/target/site}}, there exists a directory
called {{cobertura}} and
{{project-reports.html}} in the directory has a link pointing to
{{cobertura/index.html}}.
With 2.5, when going into {{MODULE/target/site}}, there does not exist a
directory called {{cobertura}} and
{{project-reports.html}} in the directory has a link pointing to {{index.html}}.
I will attach the complete console output for 2.4 and 2.5.
> Regression: report will not be rendered on invocation of mvn clean install
> site for a multi module project.
> -----------------------------------------------------------------------------------------------------------
>
> Key: MCOBERTURA-145
> URL: http://jira.codehaus.org/browse/MCOBERTURA-145
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Environment: maven-3.0.3, maven-cobertura-plugin 2.5
> Reporter: Mirko Friedenhagen
> Attachments: cobertura-2.4.log, cobertura-2.5.log
>
>
> When switching from 2.4 to 2.5 invocation of {{mvn clean install site}} will
> not render neither the html nor the xml report anymore in a multimodule
> project. A test project may be found at:
> https://github.com/mfriedenhagen/multi-module-sample/commit/62c5ec2d8bfc1c0420f7e6a701032300894eaa98.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
