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

Vincent Siveton moved MNG-3476 to MSHARED-13:
---------------------------------------------

    Component/s:     (was: Shared)
                     (was: Sites & Reporting)
                 maven-reporting-impl
            Key: MSHARED-13  (was: MNG-3476)
        Project: Maven Shared Components  (was: Maven 2)

> [maven-reporting-impl] 2.0.4 uses old doxia-site-renderer with obsolete 
> Renderer.createSink(..) call
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MSHARED-13
>                 URL: http://jira.codehaus.org/browse/MSHARED-13
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-reporting-impl
>            Reporter: John Casey
>            Assignee: John Casey
>            Priority: Critical
>
> AbstractMavenReport calls Renderer.createSink(..) which is obsolete. The 
> doxia-site-renderer 1.0-alpha-10 release is newest, and Renderer interface in 
> that release doesn't contain this method...The site plugin avoids this 
> problem by creating its own Sink and side-stepping the call in 
> AbstractMavenReport, but this leaves plugin:report (for instance) to fail 
> when called on its own.
> Since the 2.0.4 release of reporting-impl, many changes have been 
> incorporated, such that I cannot guarantee we won't see significant other 
> problems if we try to use it. (there are several abstract methods that seem 
> to have literally disappeared out of AbstractMavenReport, for example). I've 
> created a copy of the 2.0.4 tag for this project into:
> https://svn.apache.org/repos/asf/maven/shared/branches/maven-reporting-impl-2.0.4.1-dev
> to allow us to make a much smaller updated release without all the other 
> changes, just to help stabilize plugins like the maven-plugin-plugin.

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

        

Reply via email to