[jira] Issue Comment Edited: (MPLUGIN-104) plugin report broken in 2.4

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MPLUGIN-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128057 ] 

bentmann edited comment on MPLUGIN-104 at 3/20/08 2:47 PM:
--------------------------------------------------------------------

Somehow this stack trace looks familar: MCHANGES-88.

Dennis had the same problem with the l10n-plugin over at Mojo and could "cure" it by downgrading to doxia 1.0-alpha-7, see [plugin's promotion vote|http://www.nabble.com/-VOTE--Promote-Localization-Tools-Maven-Plugin-from-the-sandbox-to15916797.html#a15926961].

Maybe a newer release of the maven-reporting-impl is due to catch up with doxia.

      was (Author: bentmann):
    Somehow this stack trace looks familar: MCHANGES-88

Maybe a newer release of the maven-reporting-impl is due catch up with doxia.
  
> plugin report broken in 2.4
> ---------------------------
>
>                 Key: MPLUGIN-104
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-104
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Bug
>          Components: Plugin Plugin
>    Affects Versions: 2.4
>            Reporter: Brian Fox
>
> In 2.4 with 2.0.8 I get:
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink;
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.createSink(Ljava/io/File;Ljava/lang/String;)Lorg/apache/maven/doxia/siterenderer/sink/SiteRendererSink;
> 	at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:63)
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:324)
> 	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> 	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> 	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> 	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}

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