You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason Dillon <ja...@planet57.com> on 2007/04/07 00:50:01 UTC

mvn site not happy for archetype plugins

I was just trying to get a site for my archetype plugin, but its  
spitting out:

<snip>
java.lang.NullPointerException
         at  
org.apache.maven.tools.plugin.generator.PluginXdocGenerator.execute 
(PluginXdocGenerator.java:46)
         at  
org.apache.maven.plugin.plugin.PluginReport.generatePluginDocumentation( 
PluginReport.java:192)
         at org.apache.maven.plugin.plugin.PluginReport.executeReport 
(PluginReport.java:141)
         at org.apache.maven.reporting.AbstractMavenReport.generate 
(AbstractMavenReport.java:98)
         at  
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument 
(ReportDocumentRenderer.java:67)
         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.executeGoalWithLifec 
ycle(DefaultLifecycleExecutor.java:480)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
(DefaultLifecycleExecutor.java:459)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle 
Failures(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:272)
         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)
</snip>

Any idea why this is happening?

Does an archetype module really need to be '<packaging>maven-plugin</ 
packaging>'?

--jason

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: mvn site not happy for archetype plugins

Posted by Raphaël Piéroni <ra...@gmail.com>.
2007/4/7, Jason Dillon <ja...@planet57.com>:
>
> Does an archetype module really need to be '<packaging>maven-plugin</
> packaging>'?
I would have answered: to inherit the plugin-metadata

Raphaël