You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Bob Allison (JIRA)" <ji...@codehaus.org> on 2005/08/19 15:30:08 UTC
[jira] Commented: (MNG-754) Exception thrown building site
[ http://jira.codehaus.org/browse/MNG-754?page=comments#action_44741 ]
Bob Allison commented on MNG-754:
---------------------------------
Looking at the artifact that it is complaining about, it is one that depends on a jar which I copied from my app server's library and placed in the repository so I could use it as a dependency. It appears to be caused by the fact that I did not create a POM for the app server's library jar. When I built the POM, the problem goes away.
I should also mention that the problem only seems to appear when running in reactor mode. If I go directly to the project having problems, the site builds fine.
> Exception thrown building site
> ------------------------------
>
> Key: MNG-754
> URL: http://jira.codehaus.org/browse/MNG-754
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Fix For: 2.0-beta-1
> Attachments: ActiveProjectArtifact.diff
>
>
> Starting a new project which depends on another project in my tree. I created the bare bones project directory and added an index.xml in the src/site/xdoc directory.
> When trying to build the site from the top level project, I got the following exception in the new project:
> [INFO] [site:site]
> [INFO] Generate "JavaDocs" report.
> [INFO] Generate "Issue Tracking" report.
> [INFO] Generate "Dependencies" report.
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error during site generation
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error during site generation
> at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:500)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:433)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> 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)
> Caused by: java.lang.IllegalArgumentException: Can't find a valid Maven project in the repository for the artifact [org.apache.maven.project.artifact.ActiveProjectArtifact@1d03ef].
> at org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:236)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:147)
> at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117)
> at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:298)
> ... 16 more
> I think the exception needs to have the actual artifact information. Perhaps the ActiveProjectArtifact class needs a toString method to fix this.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org