[
http://jira.codehaus.org/browse/MCOBERTURA-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107837
]
Jörg Hohwiller commented on MCOBERTURA-63:
------------------------------------------
The patch was already applied to the trunk as you can read in the comments
above. The previous problem was that this was after the latest SNAPSHOT was
build. So you do not need to apply the patch.
> empty index.html when site is staged.
> -------------------------------------
>
> Key: MCOBERTURA-63
> URL: http://jira.codehaus.org/browse/MCOBERTURA-63
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1, 2.2
> Environment: winXP, linux
> maven 2.0.4,2.0.5
> Reporter: Jörg Hohwiller
> Assignee: Dennis Lundberg
> Fix For: 2.2
>
> Attachments: MCOBERTURA-63.patch
>
>
> When cobertura report is used together with "site:stage", the report only
> contains an empty index.html file.
> I tried it with all versions of covertura-maven-plugin I could get including
> the latest from trunk.
> For more details please consider MSITE-138 (includes test-project to prove
> the bug).
> I expected this to be the same as MSITE-120 which also was the fix for
> MJXR-20.
> Anyhow I saw in the latest version from trunk, that you use this:
> /**
> * The output directory for the report.
> *
> * @parameter
> default-value="${project.reporting.outputDirectory}/cobertura"
> * @required
> */
> private File outputDirectory;
> Anyhow the stuff does NOT go to ${project.reporting.outputDirectory} but to
> ${project.build.directory}.
> I compared your work with the latest JXR where the analog problem has been
> fixed and the only difference I found was that they use
> maven-reporting-impl:2.0.2 instead of 2.0 which is used by cobertura.
> So I hacked your pom and saw that I had to fix various parts in the code so
> the stuff still compiles. Then I discovered that a testcase failed. After I
> fixed all this I discovered that my work was in vain - the problem is still
> there!
> For me this looks like a bug in the maven internals (plugin-plugin, or so)
> that is NOT properly injection the outputDirectory. I still have no clue what
> is different to javadoc and jxr here...
> Good luck ;)
--
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
