NPE when generating "Scm ChangeLog" report

Well, there may be some issues with multi-modules project because we don't have tags and trunk per module but for the whole project so we don't differentiate entries between each modules. When we tried it we got the same report for each submodules.
Could you please provide more infos concerning your configuration, was it from the parent pom or from one of the sub-modules ?
Also you should set the -e flag so that we could have some logs.
Emmanuel

Sorry for the delay, it took some time to reproduce.

Plug-in is configured in parent pom and is inherited by sub-modules (some of which are multi-module projects themselves). When report is run for first "leaf" module it breaks with NPE if I don't configure "tagBase" configuration element. Both project.scm.connection and project.scm.developerConnection point to project svn's "trunk" directory. Here is complete configuration:

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>scmchangelog-maven-plugin</artifactId>
<version>1.0</version>
<configuration>
<dateFormat>yyyy-MM-dd</dateFormat>
<grammar>MANU</grammar>
<timestampFormat>dd/MM/yyyy HH:mm</timestampFormat>
<trackerType>${project.issueManagement.system}</trackerType>
<trackerUrlPattern>${project.issueManagement.url}</trackerUrlPattern>

<connectionType>connection</connectionType>
<connectionUrl>${project.scm.connection}</connectionUrl>
<developerConnectionUrl>${project.scm.developerConnection}</developerConnectionUrl>
<!--
<tagBase>scm:svn:https://svn.foo.bar.com/project/tags</tagBase>
-->
</configuration>
</plugin>

Ok,
There seems to be a problem getting entries from the tag url. As the code is a derivative from maven-scm-plugin 1.1-SNAPSHOT so I will have to look into it.
Could you please try it again with the 1.0 version so I could be sure of the line number as I don't see anything null on the line 131 ?

Emmanuel

Stack trace seems to be the same in 1.0 as in 1.0-SNAPSHOT. One part I've left out in first comment was that there was a SEVER error logged just before the stack trace. Here is the log:

Oct 16, 2008 5:13:05 PM org.codehaus.mojo.scmchangelog.scm.svn.SvnChangeLogCommand executeChangeLogCommand
SEVERE: The svn command failed.svn: Unable to find repository location for 'https://svn.acme.com/project/trunk/module1/submodule1' in revision 578

[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at org.codehaus.mojo.scmchangelog.scm.ScmAdapter.getSvnListOfReleases(ScmAdapter.java:131)
at org.codehaus.mojo.scmchangelog.scm.ScmAdapter.getListOfReleases(ScmAdapter.java:93)
at org.codehaus.mojo.scmchangelog.ScmActivityReport.executeReport(ScmActivityReport.java:330)
at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:105)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:585)
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)

I got the same problem in a multi module project and I think it is related to projects that don't exist in some revisions. For instance my project eclipse-floggy-plugin don't exist in revision 110 (http://floggy.svn.sourceforge.net/viewvc/floggy/?pathrev=110).

SEVERE: The svn command failed.svn: Unable to find repository location for 'https://floggy.svn.sourceforge.net/svnroot/floggy/tags/floggy-1.2.0/eclipse-floggy-plugin' in revision 110

[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at org.codehaus.mojo.scmchangelog.scm.ScmAdapter.getSvnListOfReleases(ScmAdapter.java:131)
at org.codehaus.mojo.scmchangelog.scm.ScmAdapter.getListOfReleases(ScmAdapter.java:93)
at org.codehaus.mojo.scmchangelog.ScmActivityReport.executeReport(ScmActivityReport.java:330)
at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
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)

This patch fixes the problem.

Index: src/main/java/org/codehaus/mojo/scmchangelog/scm/ScmAdapter.java
===================================================================
— src/main/java/org/codehaus/mojo/scmchangelog/scm/ScmAdapter.java (revision 8955)
+++ src/main/java/org/codehaus/mojo/scmchangelog/scm/ScmAdapter.java (working copy)
@@ -130,9 +130,12 @@
fileSet,
getScmVersion( SvnTargetEnum.TRUNK, tag.getStartRevision() ),
getScmVersion( SvnTargetEnum.TRUNK, tag.getEndRevision() ), "" );

• Release release = new Release( tag,
• logs.getChangeLog().getChangeSets() );
• releases.add( release );
  +
  + if (logs.getChangeLog() != null) { + Release release = new Release( tag, + logs.getChangeLog().getChangeSets() ); + releases.add( release ); + }
  }
  String endRevision = "0";
  if ( !tags.isEmpty() )

Patch applied.
Thanks Thiago