This has just been filed: http://jira.codehaus.org/browse/MPIR-212
I haven't had time to look at it yet, please track your findings there.
Cheers,
-Lukas
On 12/14/2010 01:52 PM, Jörg Schaible wrote:
Hi,
I have currently a problem with the maven-project-info-report-plugin, that
fails to create the project summary:
=========== %< ============
[DEBUG] Generating /home/jos/work/projects/qmb/target/site/project-
summary.html
[INFO] Generating "Project Summary" report.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error during page generation
Embedded error: Error rendering Maven report: error while invoking generate
basedir /home/jos/work/projects/qmb/src/main/java does not exist
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
generation
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
generation
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:123)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
rendering Maven report: error while invoking generate
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:171)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:118)
... 19 more
Caused by: org.apache.maven.reporting.MavenReportException: error while
invoking generate
at
org.apache.maven.plugins.site.ReportDocumentRenderer.generateMultiPage(ReportDocumentRenderer.java:248)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:157)
... 23 more
Caused by: java.lang.reflect.InvocationTargetException
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.apache.maven.plugins.site.ReportDocumentRenderer.generateMultiPage(ReportDocumentRenderer.java:226)
... 24 more
Caused by: java.lang.IllegalStateException: basedir
/home/jos/work/projects/qmb/src/main/java does not exist
at
org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
at
org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
at
org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
at
org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
at
org.apache.maven.report.projectinfo.ProjectSummaryReport$ProjectSummaryRenderer.isJavaProject(ProjectSummaryReport.java:290)
at
org.apache.maven.report.projectinfo.ProjectSummaryReport$ProjectSummaryRenderer.renderBody(ProjectSummaryReport.java:131)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.ProjectSummaryReport.executeReport(ProjectSummaryReport.java:55)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
... 29 more
=========== %< ============
The problem is quite obvious, the question is, why is it suddenly triggered?
When I build an ear with the same set of plugins I also don't have a
src/main/java directory, but the project summary is created. Therefore it
seems somehow also related to the project itself. That one is build by a
custom plugin (more or less a very specialized assembly plugin generating a
ZIP file). The project is of custom type "qmb" and the plugin contains
following component.xml:
=========== %< ============
<component-set>
<components>
<component>
<role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
<role-hint>qmb</role-hint>
<implementation>org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping</implementation>
<configuration>
<phases>
<generate-resources>com.scalaris.maven2.plugin:scalaris-qmb-
plugin:generate</generate-resources>
<process-resources>org.apache.maven.plugins:maven-resources-
plugin:resources</process-resources>
<package>com.scalaris.maven2.plugin:scalaris-cs-qmb-
plugin:pack</package>
<install>org.apache.maven.plugins:maven-install-
plugin:install</install>
<deploy>org.apache.maven.plugins:maven-deploy-
plugin:deploy</deploy>
</phases>
</configuration>
</component>
<component>
<role>org.apache.maven.artifact.handler.ArtifactHandler</role>
<role-hint>qmb</role-hint>
<implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation>
<configuration>
<extension>zip</extension>
<type>qmb</type>
<packaging>qmb</packaging>
<language>java</language>
<addedToClasspath>false</addedToClasspath>
<includesDependencies>true</includesDependencies>
</configuration>
</component>
</components>
</component-set>
=========== %< ============
I tried to drop the language element in the component descriptor above and I
tried also a version with that element being empty. The plugin is built
against the artifacts of Maven 2.2.1.
The problem occurs running Maven 2.2.1 with site plugin 2.2 and report-info-
plugin 2.3. Downgrading PIR to 2.2 solves it.
For Maven 3 in combination with site 3.0-beta-3 and PIR 2.3, the project
summary generation works, but the javadoc plugin fails with a NPE because
target/site/apidocs dos not exists. Again a problem triggered by the Java
nature.
Apart from the regression I don't understand what triggers the Java handling
while the ear plugin does obviously not. Therefore I struggle to create a
test case here.
Any advice welcome,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
