maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <>
Subject [jira] Commented: (MSHARED-120) Unable to generate single report with latest maven-reporting-impl
Date Mon, 24 Aug 2009 20:51:41 GMT


Dennis Lundberg commented on MSHARED-120:

Well, in that case I do not understand how it could have worked with versions prior to Doxia
1.0. I have diffed maven-reporting-impl with, doxia-sink-api, doxia-core and
doxia-site-renderer 1.0-alpha-10 with 1.0, and I cannot find any changes in there that would
make things stop working.

No I didn't try your samples, but if you say it doesn't work, I trust you on that. unfortunately
I do not understand how to fix it, but I am willing to help in any way I can, doing releases
or whatever.

> Unable to generate single report with latest maven-reporting-impl
> -----------------------------------------------------------------
>                 Key: MSHARED-120
>                 URL:
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-reporting-impl
>    Affects Versions: maven-reporting-impl, maven-reporting-impl
>            Reporter: Vincent Siveton
>            Priority: Blocker
>         Attachments: MSHARED-120.patch, reporting.patch
> Recently, I fixed several report plugins (changelog, changes etc.) to use Doxia 1.0 and
latest maven-reporting-impl.
> The main goal was to make reporting plugins available in PDF (see MPDF-26 and doc [1])
> I notified that running a single report doesn't work but works when coupling with maven-site-plugin
> For instance, run:
> {noformat}
> mvn org.apache.maven.plugins:maven-changelog-plugin:2.2-SNAPSHOT:changelog
> {noformat}
> In Doxia 1.0, the SiteRenderSink [2] uses a StringWriter by default to use getBody()
in the renderer [3]. So running a single report doesn't write a file with reporting-impl:
> In MPIR 2.1.2, we overrided the mojo.execute() to handle a default renderer [4] so we
are able to run a single report. I propose to move this logic in AbstractMavenReport.
> [1]
> [2]
> [3]
> [4]

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message