You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2009/11/03 14:54:55 UTC

[jira] Closed: (MSHARED-120) No single report generated with latest maven-reporting-impl

     [ http://jira.codehaus.org/browse/MSHARED-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Siveton closed MSHARED-120.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: maven-reporting-impl 2.0.4.3
         Assignee: Vincent Siveton

fixed in [r832410|http://svn.apache.org/viewvc?rev=832410&view=rev]

> No single report generated with latest maven-reporting-impl
> -----------------------------------------------------------
>
>                 Key: MSHARED-120
>                 URL: http://jira.codehaus.org/browse/MSHARED-120
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-reporting-impl
>    Affects Versions: maven-reporting-impl 2.0.4.1, maven-reporting-impl 2.0.4.2
>            Reporter: Vincent Siveton
>            Assignee: Vincent Siveton
>            Priority: Blocker
>             Fix For: maven-reporting-impl 2.0.4.3
>
>         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 2.0.x.
> 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:2.0.4.2
> 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] http://maven.apache.org/plugins/maven-pdf-plugin-1.1-SNAPSHOT/examples/configuring-reports.html#Maven_Reporting_Plugins_Issues
> [2] http://maven.apache.org/doxia/doxia-sitetools-1.0.x/xref/org/apache/maven/doxia/siterenderer/sink/SiteRendererSink.html#47
> [3] http://maven.apache.org/doxia/doxia-sitetools-1.0.x/xref/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.html#433
> [4] http://maven.apache.org/plugins/maven-project-info-reports-plugin/xref/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.html#137

-- 
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