You are viewing a plain text version of this content. The canonical link for it is here.
Posted to doxia-users@maven.apache.org by Matthew Pocock <ma...@ncl.ac.uk> on 2008/05/13 23:16:49 UTC
npe
Hi,
When building my maven site, I'm now getting a NPE. If I build the site again,
the site builds fine. If I maven clean first, and then build, the NPE comes
back.
The exception isn't being very informative about what may be wrong. In
particular, it's not giving me any hint about what file the problem was
encountered in. Any hints?
Matthew
java.lang.NullPointerException
at
org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:467)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:92)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:53)
at
org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
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:129)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
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.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
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)
Re: npe
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Matthew,
Create an issue with your svn link and add a full stack trace.
Also, specify some steps to reproduce it.
Cheers,
Vincent
2008/5/14, Matthew Pocock <ma...@ncl.ac.uk>:
> Hi,
>
> I am not having much luck making a reproducible test-case. With three
> xdocs to process, it seems to be random which one (if any) fails to build.
> Different hashcodes making iteration order different on different runs?
>
> If you like, I can point you at the right svn URL to reproduce my problem.
>
>
> Matthew
>
>
> >
> > From the reported line number it must be a problem with some macro in
> > an xdoc file. Can you try to track it down and attach a reproducible
> > test case to jira?
> >
> > Thanks,
> > -Lukas
> >
> >
> > Matthew Pocock wrote:
> >> Hi,
> >>
> >> When building my maven site, I'm now getting a NPE. If I build the site
> >> again,
> >> the site builds fine. If I maven clean first, and then build, the NPE
> >> comes
> >> back.
> >>
> >> The exception isn't being very informative about what may be wrong. In
> >> particular, it's not giving me any hint about what file the problem was
> >> encountered in. Any hints?
> >>
> >> Matthew
> >>
> >>
> >> java.lang.NullPointerException
> >> at
> >> org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:467)
> >> at
> >> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:92)
> >> at
> >> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:53)
> >> at
> >> org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
> >> at
> >> org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
> >> at
> >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
> >> at
> >> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
> >> 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:129)
> >> at
> >> org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> >> 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.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> >> 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)
> >>
> >
>
>
>
Re: npe
Posted by Matthew Pocock <ma...@ncl.ac.uk>.
Hi,
I am not having much luck making a reproducible test-case. With three
xdocs to process, it seems to be random which one (if any) fails to build.
Different hashcodes making iteration order different on different runs?
If you like, I can point you at the right svn URL to reproduce my problem.
Matthew
>
> From the reported line number it must be a problem with some macro in
> an xdoc file. Can you try to track it down and attach a reproducible
> test case to jira?
>
> Thanks,
> -Lukas
>
>
> Matthew Pocock wrote:
>> Hi,
>>
>> When building my maven site, I'm now getting a NPE. If I build the site
>> again,
>> the site builds fine. If I maven clean first, and then build, the NPE
>> comes
>> back.
>>
>> The exception isn't being very informative about what may be wrong. In
>> particular, it's not giving me any hint about what file the problem was
>> encountered in. Any hints?
>>
>> Matthew
>>
>>
>> java.lang.NullPointerException
>> at
>> org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:467)
>> at
>> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:92)
>> at
>> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:53)
>> at
>> org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
>> at
>> org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
>> at
>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
>> at
>> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
>> 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:129)
>> at
>> org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
>> 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.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>> 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)
>>
>
Re: npe
Posted by Lukas Theussl <lt...@apache.org>.
From the reported line number it must be a problem with some macro in
an xdoc file. Can you try to track it down and attach a reproducible
test case to jira?
Thanks,
-Lukas
Matthew Pocock wrote:
> Hi,
>
> When building my maven site, I'm now getting a NPE. If I build the site again,
> the site builds fine. If I maven clean first, and then build, the NPE comes
> back.
>
> The exception isn't being very informative about what may be wrong. In
> particular, it's not giving me any hint about what file the problem was
> encountered in. Any hints?
>
> Matthew
>
>
> java.lang.NullPointerException
> at
> org.apache.maven.doxia.module.xdoc.XdocParser.handleEndTag(XdocParser.java:467)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:92)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:53)
> at
> org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
> 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:129)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> 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.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> 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)
>