Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0
-
Fix Version/s: None
-
Component/s: analyze
-
Labels:None
-
Environment:maven 2.0.8
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
-
Testcase included:yes
-
Number of attachments :
Description
mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:analyze-report fails with:
[INFO] [dependency:analyze-report]
[INFO] /u/david/projects/codehaus/mojo/mojo/was6-maven-plugin/target
[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] ------------------------------------------------------------------------
[INFO] 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:597)
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)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 44 seconds
[INFO] Finished at: Tue Apr 01 22:14:23 CEST 2008
[INFO] Final Memory: 14M/25M
[INFO] ------------------------------------------------------------------------
This can be tested on for example:
svn co https://svn.codehaus.org/mojo/trunk/mojo/was6-maven-plugin test
cd test && mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:analyze-report
Issue Links
| This issue relates to: | ||||
| MCHANGES-88 | NoSuchMethodError with maven 2.0.8 when generating changes-report |
|
|
|
From IRC:
22:34 < ltheussl> there is no method createSink in siterenderer.Renderer
22:35 < ltheussl> and I don't remember that anything changed there
22:35 < ltheussl> I can reproduce it but I don't understand the error
22:37
!jason [~jvanzyl@c-67-180-48-143.hsd1.ca.comcast.net] has joined #maven22:39
!pombreda [~pombreda@c-67-180-198-25.hsd1.ca.comcast.net] has quit [Ping timeout]22:39 < ltheussl> ai, seems the same as this: http://jira.codehaus.org/browse/MCHANGES-88
22:42 < Brian> yep
!jason [~jvanzyl@c-67-180-48-143.hsd1.ca.comcast.net] has joined #maven 22:39!pombreda [~pombreda@c-67-180-198-25.hsd1.ca.comcast.net] has quit [Ping timeout] 22:39 < ltheussl> ai, seems the same as this: http://jira.codehaus.org/browse/MCHANGES-88 22:42 < Brian> yep