[ http://jira.codehaus.org/browse/MSITE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Ferguson updated MSITE-255: ----------------------------------- Attachment: dev-200.zip Dennis, its caused by the faq.fml not having any faq elements within the part element, which causes the Part class in doxia-1.0-alpha-8 to be incompletely formed. We typically have such an entry for new projects for which there are no FAQ entries yet. Eg {code} <?xml version="1.0"?> <faqs id="FAQ" title="Frequently Asked Questions"> <part id="General"> <!-- Add FAQs as they get asked. <faq id="Why is buildinfo run during the test phase"> <question>Why is buildinfo run during the test phase?</question> <answer> <p> The prepare-package phase will be introduced in Maven 2.1, and build info will be bound to this phase. <br/> <br/> Currently the buildinfo plugin is bound to the test phase, so it is run before the package phase. This way the buildinfo file is included in the JAR </p> </answer> </faq> --> </part> </faqs> {code} It manifests like so: {code} [INFO] Trace java.lang.NullPointerException at org.apache.maven.doxia.module.fml.FmlParser.createSink(FmlParser.java:270) at org.apache.maven.doxia.module.fml.FmlParser.parse(FmlParser.java:61) at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:52) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:264) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:43) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) [INFO] ------------------------------------------------------------------------ {code} This was fixed in doxia-1.0-alpha-10 (which is used by the maven-site-plugin-2.0-beta-6-SNAPSHOT) and I have verified that the site gets successfully generated with it. So you can mark it as fixed for 2.0-beta-6. Must be almost time for a release? > Executing the site-site goal fails prior to executing the site-deploy goal on > a clean maven install (Could be due to dependencies) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: MSITE-255 > URL: http://jira.codehaus.org/browse/MSITE-255 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Affects Versions: 2.0-beta-5 > Environment: Windows XP, Java 1.5, Intel Pentium 4 > Reporter: Sahand > Attachments: dev-200.zip > > > When running {{mvn site:site}} from a clean maven install I get FATAL ERROR > caused by a NullPointerException. (*Trace log below*) > This was resolved by running {{mvn site:deploy}} which seemed to retrieve a > series of dependent libraries. After which, running {{mvn site:site}} would > execute successfully. > I will test it again when I get the time to narrow down the dependency that > is required for execution and is not being retrieved. > {quote} > [ERROR] FATAL ERROR > [INFO] > --------------------------------------------------------------------- > --- > [INFO] null > [INFO] > --------------------------------------------------------------------- > --- > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.doxia.module.fml.FmlParser.createSink(FmlParser.java > :270) > at > org.apache.maven.doxia.module.fml.FmlParser.parse(FmlParser.java:61) > at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:52) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocumen > t(DefaultSiteRenderer.java:264) > at > org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocum > ent(DoxiaDocumentRenderer.java:43) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule( > DefaultSiteRenderer.java:239) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul > tSiteRenderer.java:115) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124 > ) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > 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) > [INFO] > --------------------------------------------------------------------- > --- > [INFO] Total time: 26 seconds > [INFO] Finished at: Wed Aug 29 12:49:50 EST 2007 > [INFO] Final Memory: 25M/44M > [INFO] > --------------------------------------------------------------------- > {quote} -- 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