stat-scm-user

[Stat-scm-user] Error generating report

[Ed H. <ed....@gm...>]

OK, I've updated my Maven project to include the stat-scm, and it
looks like it's chugging away.  I'm getting all these INFO messages
like...

INFO:    csrwebgui/src/main/java/com/intecbilling/csrwebgui/view/LogonBean.java,
on r66, +2 -0
Jul 24, 2008 3:34:08 PM net.sf.statsvn.util.JavaUtilTaskLogger info

So, I presume it's going through the log file.  Fantastic.  But then
it errors with the following message:

[INFO] Generating "StatSCM" report.
[INFO] StatSCM - generating source code management metrics.
[INFO] StatSCM Version: (1.1.0)
[INFO] Configuring StatXXX
[INFO] Include all
[INFO] Exclude none
[INFO] SCM Connection Type :svn
[INFO] Output Directory
:/u01/ct/acct/ehillman/webgui-src/trunk/webgui/target/generated-site/xdoc/statscm/
[INFO] scm log >
/u01/ct/acct/ehillman/webgui-src/trunk/webgui/target/generated-site/xdoc/statscm/scm.log
[INFO] /u01/ct/acct/ehillman/webgui-src/trunk/webgui/target/generated-site/xdoc/statscm/scm.log
EOF.
[INFO] scm log ...; exitValue: 0
[WARNING] Null Pointer: Sometimes happens when local files are not
synced with the repository!
[ERROR]
java.lang.NullPointerException
	at net.sf.statsvn.input.SvnLogfileParser$PerRevDiffTask.run(SvnLogfileParser.java:784)
	at net.sf.statsvn.input.SvnLogfileParser.executeTask(SvnLogfileParser.java:216)
	at net.sf.statsvn.input.SvnLogfileParser.handleLineCounts(SvnLogfileParser.java:201)
	at net.sf.statsvn.input.SvnLogfileParser.parse(SvnLogfileParser.java:343)
	at net.sf.statsvn.Main.generateDefaultHTMLSuite(Main.java:278)
	at net.sf.statsvn.Main.generateDefaultHTMLSuite(Main.java:240)
	at net.sf.statscm.StatScmMojo.doSvnStats(StatScmMojo.java:255)
	at net.sf.statscm.StatScmMojo.executeReport(StatScmMojo.java:219)
	at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
	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:133)
	at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
	at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:117)
	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: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)

Now, my working copy is up-to-date with the repository, so I'm not
sure what this message means.  One of the last files being processed
(that I can see in those INFO messages) is an old file which has been
deleted in the HEAD of the code base.  Could it be that it's trying to
find the file in the working copy, but it's not there because it's
been svn removed a long time ago?

Otherwise, I have no idea about what it going wrong here.  Any help
would be greatly appreciated.

Thanks,
Ed

Re: [Stat-scm-user] Error generating report

[Martin K. <mar...@cu...>]

Ed Hillmann wrote:
> OK, I've updated my Maven project to include the stat-scm, and it
> looks like it's chugging away.
[...]
> it errors with the following message:
>
> [WARNING] Null Pointer: Sometimes happens when local files are not
> synced with the repository!
> [ERROR]
> java.lang.NullPointerException
>  at net.sf.statsvn.input.SvnLogfileParser$PerRevDiffTask.run
>     (SvnLogfileParser.java:784)

Looks to me like a problem in StatSVN (given that the NullPointerException
happens in a class in a net.sf.statsvn-package).

StatSCM is a "Maven-enabler" build on top of two separate projects:
StatCVS and StatSVN.

You might want to see if the folks over at the StatSVN project [1] can
offer some help, since it has been pretty quiet on this list.

As far as I understand you are using StatSCM v1.1.0 released 2008-04-06,
which according to the StatSCM news section [2] use StatSVN 0.4. (This
seems a bit odd to me since the StatSVN project page announces the release
of v0.4 at a later date, namely 2008-05-04, so if reporting the
stack-trace to the StatSVN-team beware that it might in fact be a
pre-release of v0.4 with different source code and line numbers.)

Good luck from another user!
Regards,
 Martin

References:
 [1] http://www.statsvn.org/ - The StatSVN project
 [2] http://stat-scm.sourceforge.net/ - The StatSCM project; see "News"

Re: [Stat-scm-user] Error generating report

[Ed H. <ed....@gm...>]

> Looks to me like a problem in StatSVN (given that the NullPointerException
> happens in a class in a net.sf.statsvn-package).
>
> StatSCM is a "Maven-enabler" build on top of two separate projects:
> StatCVS and StatSVN.
>
> You might want to see if the folks over at the StatSVN project [1] can
> offer some help, since it has been pretty quiet on this list.
>
> As far as I understand you are using StatSCM v1.1.0 released 2008-04-06,
> which according to the StatSCM news section [2] use StatSVN 0.4. (This
> seems a bit odd to me since the StatSVN project page announces the release
> of v0.4 at a later date, namely 2008-05-04, so if reporting the
> stack-trace to the StatSVN-team beware that it might in fact be a
> pre-release of v0.4 with different source code and line numbers.)
>
> Good luck from another user!
> Regards,
>  Martin

Thanks for the feedback, Martin.  I wasn't aware how it all hung
together,  In order to understand what was going on, I downloaded the
latest version of StatSVN (0.4.1) and attempted to generate the
reports directly using StatSVN (instead of using the plugin).  And
they all generated fine.

I think there were some changes between 0.4.0 and 0.4.1 that addressed
what is causing my problem (property-only changes in the Subversion
revision).  As the current version of StatSCM is using an earlier
version of StatSVN, I'm just waiting for a new release of the plugin
that will use the newer version of StatSVN.

Thanks again,
Ed