Thanks to Wendy, I am now running mvn site:run so I can see my changes
straight away instead of waiting for mvn site to finish.

When I browse to a page I get the following error:

[INFO] [site:run]
:INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
[WARNING] Unable to load parent project from repository: Could not
find the model file
'D:\ide\workspace\maven\pde-maven-plugin\..\pom.xml'.
[INFO] Starting Jetty on http://localhost:8080/
:INFO:  NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet
:INFO:  Started SelectChannelConnector @ 0.0.0.0:8080
[INFO] Generate "About" report.
[ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
[ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
:WARN:  /css/maven-theme.css
java.util.ConcurrentModificationException
       at 
java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
       at java.util.AbstractList$Itr.next(AbstractList.java:420)
       at 
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:132)
       at 
org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:102)
       at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:869)
       at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:348)
       at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:174)
       at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:220)
       at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:536)
       at org.mortbay.jetty.Server.handle(Server.java:331)
       at org.mortbay.jetty.Server.handle(Server.java:301)
       at org.mortbay.jetty.HttpConnection.doHandler(HttpConnection.java:351)
       at org.mortbay.jetty.HttpConnection.access$1500(HttpConnection.java:38)
       at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:598)
       at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:489)
       at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:198)
       at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:289)
       at 
org.mortbay.jetty.nio.SelectChannelConnector$HttpEndPoint.run(SelectChannelConnector.java:710)
       at 
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:412)

I am going to assume the failed parent pom warning can be ignored (as
it usually can, it should be getting parent from the local m2
repository)

I am going to assume the errors about VM macros being incorrect can be
ignored (mvn site spits out large numbers of them and it builds the
web site correctly)

However I have no idea why  /css/maven-theme.css is causing this exception.
/css/site.css and /css/maven-base.css also throw this exception.

The page still displays, but it looks ugly since none of the CSS files
appear to be applied.

Has anyone else had this problem?

Cheers
Barrie

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to