Thread: [Stat-scm-user] Fwd: Does not update reports
Brought to you by:
benoitx,
dougculnane
From: sandeep r. <san...@gm...> - 2010-07-29 14:41:10
|
Hello, Yesterday evening I was looking at the stat-scm reports not being updated. I’ve checked the logs for the report and found several NullPointerException like the one pasted below. Have you encountered anything like this before? Any clue? 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:220) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:164) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:158) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:120) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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) Sandeep ---------- Forwarded message ---------- From: sandeep reddy <san...@gm...> Date: Wed, Jul 28, 2010 at 1:44 PM Subject: Does not update reports To: sta...@li... Hello, I have a question, I'm using stat-scm for generating project reports. I see that it does not update reports (nothing changed in configuration). When I open the site to view the reports, it does not update the new results. Any clue? -- Thanks, Sandeep -- Thanks, Sandeep |
From: sandeep r. <san...@gm...> - 2010-08-09 15:35:36
|
I use the statscm plugin from my project pom file. I use continuum site-deloy to generate reports for the project. The reports are to be generated in www/html/maven/site/project directory. For some reason I notice that the statscm directory in www/html/maven/site/project contains only the statscm.html, and not the other generated files. Any help would be appreciated. On Fri, Jul 30, 2010 at 2:28 AM, Doug Culnane <dou...@gm...> wrote: > Maybe you have not checked out the HEAD? Look at the output of the svn log > file. This is what the reports are based on. > > All the best, > > Doug > > > On Thu, Jul 29, 2010 at 6:58 PM, sandeep reddy <san...@gm...>wrote: > >> I already did that. But it doesn't update the reports for some reason. >> >> >> On Thu, Jul 29, 2010 at 9:58 AM, Doug Culnane <dou...@gm...>wrote: >> >>> You should do an subversion update then a mvn site to create a new >>> version of the site. This can be done with a script and a timed job on a >>> server. To deploy the site use mvn site:deploy. >>> >>> svn up >>> mvn site site:deploy >>> >>> >>> >>> All the best, >>> >>> Doug >>> >>> >>> >> >> >> -- >> Thanks, >> Sandeep >> > > -- Thanks, Sandeep |
From: Doug C. <dou...@gm...> - 2010-07-29 14:58:57
|
You should do an subversion update then a mvn site to create a new version of the site. This can be done with a script and a timed job on a server. To deploy the site use mvn site:deploy. svn up mvn site site:deploy All the best, Doug |