You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Julien Graglia (JIRA)" <ji...@codehaus.org> on 2007/12/13 10:23:57 UTC

[jira] Created: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

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: error.log, pom.xml

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

        

[jira] Commented: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122708 ] 

Vincent Siveton commented on MCHANGES-88:
-----------------------------------------

I fixed recently MNG-3388 so debug shoud be better specially in the realm.

The problem seems to come from MavenArtifactFilterManager wich *excludes* doxia-sink-api. We have the same problem in maven-pdf-plugin.

> 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

        

[jira] Issue Comment Edited: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Niall Pemberton (JIRA)" <ji...@codehaus.org>.
    [ 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(File, String) 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/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)

  
> 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

        

[jira] Issue Comment Edited: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118913 ] 

bentmann edited comment on MCHANGES-88 at 1/6/08 10:46 AM:
--------------------------------------------------------------------

Quite funny, reports generation works when run by the Site plugin. I attached a minimal test project and two debug logs from "mvn site" and "mvn changes:changes-report", maybe a diff on these helps.

The maven-changes-plugin directly depends on
o  maven-reporting-impl:2.0.4
o  doxia-site-renderer:1.0-alpha-9
but the maven-reporting-impl:2.0.4 itself was compiled against
o  doxia-site-renderer:1.0-alpha-7
and the method org.apache.maven.doxia.siterenderer.Renderer.createSink() does not exist any more in doxia-site-renderer:1.0-alpha-9.


      was (Author: bentmann):
    Quite funny, reports generation works when run by the Site plugin. I attached a minimal test project and two debug logs from "mvn site" and "mvn changes:changes-report", maybe a diff on these helps.

The maven-changes-plugin directly depends on
- maven-reporing-impl:2.0.4
- doxia-site-renderer:1.0-alpha-9
but the maven-reporing-impl:2.0.4 itselfs was compiled against
- doxia-site-renderer:1.0-alpha-7
and the method org.apache.maven.doxia.siterenderer.Renderer.createSink() does not exist any more in doxia-site-renderer:1.0-alpha-9.

  
> 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: changes.log, changes.zip, error.log, 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

        

[jira] Commented: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Niall Pemberton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123249 ] 

Niall Pemberton commented on MCHANGES-88:
-----------------------------------------

OK I've created MCHANGES-100

> 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
>            Assignee: Dennis Lundberg
>             Fix For: 2.0
>
>         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

        

[jira] Commented: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122690 ] 

Dennis Lundberg commented on MCHANGES-88:
-----------------------------------------

So if I understand this correctly, we really need a version maven-reporting-impl that uses the same version of doxia as this plugin does. In this case that is 1.0-alpha-9.

Until that is available we need to work around this problem. Copy the execute() method from maven-reporting-impl and modify it so that it only uses doxia-methods that are available in 1.0-alpha-9. This has already been done in MPIR, so an alternative is to copy it from there.

> 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

        

[jira] Issue Comment Edited: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Niall Pemberton (JIRA)" <ji...@codehaus.org>.
    [ 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:23 PM:
-----------------------------------------------------------------

The problem seems to be that the createSink(File, String) method was removed from org.apache.maven.doxia.siterenderer.Renderer in revision 385559:
    - 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(File, String) 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)

  
> 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

        

[jira] Closed: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg closed MCHANGES-88.
-----------------------------------

         Assignee: Dennis Lundberg
       Resolution: Fixed
    Fix Version/s: 2.0-beta-4

I committed Niall's patch in r620284. Thanks!

I left out the part for AbstractJiraDownloader though, as I was not able to reproduce it. Can you please open a separate issue for that, with instructions on how to reproduce it.

> 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
>            Assignee: Dennis Lundberg
>             Fix For: 2.0-beta-4
>
>         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

        

[jira] Issue Comment Edited: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Niall Pemberton (JIRA)" <ji...@codehaus.org>.
    [ 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

        

[jira] Commented: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Niall Pemberton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122702 ] 

Niall Pemberton commented on MCHANGES-88:
-----------------------------------------

Even when you get a compatible verson of maven-reporting-impl released it is still going to throw an exception though - just it will be a MojoExecutionException saying "Reporting mojo's can only be called from ReportDocumentRender" rather than a NoSuchMethodError.

http://svn.apache.org/repos/asf/maven/shared/trunk/maven-reporting-impl/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java

If thats considered correct maven practice and what this plugin will do once you get a maven-reporting-impl release then you may as well just implement an execute method that throws that exception now.

But if however  the report should work standalone though, then copying MPIR is the solution.



> 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

        

[jira] Updated: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MCHANGES-88:
--------------------------------------

    Attachment: site.log
                changes.log
                changes.zip

Quite funny, reports generation works when run by the Site plugin. I attached a minimal test project and two debug logs from "mvn site" and "mvn changes:changes-report", maybe a diff on these helps.

The maven-changes-plugin directly depends on
- maven-reporing-impl:2.0.4
- doxia-site-renderer:1.0-alpha-9
but the maven-reporing-impl:2.0.4 itselfs was compiled against
- doxia-site-renderer:1.0-alpha-7
and the method org.apache.maven.doxia.siterenderer.Renderer.createSink() does not exist any more in doxia-site-renderer:1.0-alpha-9.


> 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: changes.log, changes.zip, error.log, 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

        

[jira] Commented: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116843 ] 

Dennis Lundberg commented on MCHANGES-88:
-----------------------------------------

Confirming this on Windows as well with maven-site-plugin 2.0-beta-6.

> 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: error.log, pom.xml
>
>
> 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

        

[jira] Updated: (MCHANGES-88) NoSuchMethodError with maven 2.0.8 when generating changes-report

Posted by "Niall Pemberton (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MCHANGES-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niall Pemberton updated MCHANGES-88:
------------------------------------

    Attachment: MCHANGES-88-Fix-NoSuchMethodError.patch
                AbstractChangesReport.java

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