[
http://jira.codehaus.org/browse/MCHANGES-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178693#action_178693
]
Michael Osipov commented on MCHANGES-137:
-----------------------------------------
I found the bug. Its Jetty's fault. ChangesMojo is passed
#getReportOutputDirectory and jetty takes it as context root. It has under
windows a continuous file lock on all deployed files. See here:
http://docs.codehaus.org/display/JETTY/Files+locked+on+Windows
This means that the site plugin has to be patched. I dug there too and came up
with a solution, see MSITE-406. This bug can be closed when MSITE-406 is
deployed.
> On the fly generation if changes report fails
> ---------------------------------------------
>
> Key: MCHANGES-137
> URL: http://jira.codehaus.org/browse/MCHANGES-137
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes-report
> Affects Versions: 2.1
> Environment: XP SP2, Maven 2.0.9
> Reporter: Michael Osipov
>
> Just added 2.1 to my POM. Running site:run seemed fine until I hit refresh.
> An exeption has been thrown:
> {noformat}
> HTTP ERROR: 500
> Error rendering Maven report: Unable to copy static resources.
> RequestURI=/changes-report.html
> Caused by:
> org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven
> report: Unable to copy static resources.
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:149)
> at
> org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:148)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:313)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> Caused by: org.apache.maven.reporting.MavenReportException: Unable to copy
> static resources.
> at
> org.apache.maven.plugin.changes.ChangesMojo.copyStaticResources(ChangesMojo.java:124)
> at
> org.apache.maven.plugin.changes.ChangesMojo.executeReport(ChangesMojo.java:155)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
> ... 17 more
> Caused by:
> org.apache.maven.reporting.MavenReportException: Unable to copy static
> resources.
> at
> org.apache.maven.plugin.changes.ChangesMojo.copyStaticResources(ChangesMojo.java:124)
> at
> org.apache.maven.plugin.changes.ChangesMojo.executeReport(ChangesMojo.java:155)
> 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.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:148)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:313)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> Powered by Jetty://
> {noformat}
> This must be some regression, site:run worked perfectly with 2.0.
> You may reproduce with https://svn.fckeditor.net/FCKeditor.Java/trunk/ r2713.
> Set version to 2.1 in POM. and then run mvn site:run. Open up in FF,
> Introduction > Changes. Hit F5 or Ctrl+F5 > BOOM.
--
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
