maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report
Date Wed, 06 Feb 2008 02:22:29 GMT

    [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122520
] 

niallp edited comment on MCHANGES-88 at 2/5/08 8:21 PM:
-----------------------------------------------------------------

The problem seems to be that the createSink() method was removed from org.apache.maven.doxia.siterenderer.Renderer
in revision 358449:
    - http://tinyurl.com/2wh8lr

I checked out the "Project Info" reports to see if they could be run individually as well
- which they can and looking at the maven-project-info-reports-plugin - it has its own execute()
method in AbstractProjectInfoReport which all the reports in that plugin use.

I'm attaching a patch which copies the AbstractProjectInfoReport into the changes plugin,
renames it (to AbstractChangesReport) and modifies the changes and jira reports (confirmed
this has the same issue) to use that abstract implementation. This seems resolves the issue.

Running the JIRA report failed if the target directory didn't exist - so I also added code
to fix that.

In case my patch for the copied/modified AbstractProjectInfoReport  doesn't work properly,
I'm attaching a full copy of it as well (btw I copied the last 2.0.1 release version of AbstractProjectInfoReport)


      was (Author: niallp):
    The problem seems to be that the createSink() method was removed from org.apache.maven.doxia.siterenderer.Renderer
in revision 358449:
    - http://tinyurl.com/38v6bg

I checked out the "Project Info" reports to see if they could be run individually as well
- which they can and looking at the maven-project-info-reports-plugin - it has its own execute()
method in AbstractProjectInfoReport which all the reports in that plugin use.

I'm attaching a patch which copies the AbstractProjectInfoReport into the changes plugin,
renames it (to AbstractChangesReport) and modifies the changes and jira reports (confirmed
this has the same issue) to use that abstract implementation. This seems resolves the issue.

Running the JIRA report failed if the target directory didn't exist - so I also added code
to fix that.

In case my patch for the copied/modified AbstractProjectInfoReport  doesn't work properly,
I'm attaching a full copy of it as well (btw I copied the last 2.0.1 release version of AbstractProjectInfoReport)

  
> NoSuchMethodError with maven 2.0.8 when generating changes-report
> -----------------------------------------------------------------
>
>                 Key: MCHANGES-88
>                 URL: http://jira.codehaus.org/browse/MCHANGES-88
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: changes-report
>    Affects Versions: 2.0-beta-3
>         Environment: julien@jgr-pc:/opt/nc/workspace/test_maven$ mvn -version
> Maven version: 2.0.8
> Java version: 1.6.0_03
> OS name: "linux" version: "2.6.18-5-686" arch: "i386" Family: "unix"
>            Reporter: Julien Graglia
>         Attachments: AbstractChangesReport.java, changes.log, changes.zip, error.log,
MCHANGES-88-Fix-NoSuchMethodError.patch, pom.xml, site.log
>
>
> I create a simple maven2 project, but when i call
> mvn -X -e changes:changes-report
> I get an error (full log in attachment)
> 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)

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

        

Mime
View raw message