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:07:08 UTC

[jira] Created: (MNG-754) Exception thrown building site

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


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


[jira] Updated: (MNG-754) Exception thrown building site

Posted by "Bob Allison (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-754?page=all ]

Bob Allison updated MNG-754:
----------------------------

    Attachment: ActiveProjectArtifact.diff

With this patch, the exception reads:
Caused by: java.lang.IllegalArgumentException: Can't find a valid Maven project in the repository for the artifact [qaccess:logging:3.0-20050819.123446-3].

> 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


[jira] Commented: (MNG-754) Exception thrown building site

Posted by "Lilians Auvigne (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-754?page=comments#action_45453 ] 

Lilians Auvigne commented on MNG-754:
-------------------------------------

also for 
http://www.ibiblio.org/maven2/commons-beanutils/commons-beanutils-core/1.7.0/commons-beanutils-core-1.7.0.pom

with   <version>1.7</version> instead of  <version>1.7.0</version> 


> 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
>     Assignee: Vincent Siveton
>      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


[jira] Commented: (MNG-754) Exception thrown building site

Posted by "Bob Allison (JIRA)" <ji...@codehaus.org>.
    [ 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


[jira] Updated: (MNG-754) Exception thrown building site

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-754?page=all ]

Brett Porter updated MNG-754:
-----------------------------

    Fix Version: 2.0-beta-1

this should be easy to fix. the dependencies report is assuming something about the artifact it shouldn't need to, I think.

If not, it might mean that we need to ensure proper repository based resolution instead of using the activate artifacts (projects found in the reactor).

> 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

>
>
> 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


[jira] Commented: (MNG-754) Exception thrown building site

Posted by "Lilians Auvigne (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-754?page=comments#action_45452 ] 

Lilians Auvigne commented on MNG-754:
-------------------------------------

I have same problem with http://www.ibiblio.org/maven2/concurrent/concurrent/1.3.4/concurrent-1.3.4.pom.

<?xml version="1.0" encoding="ISO-8859-1"?>

<project>
  <modelVersion>1</modelVersion>
  <groupId>concurrent</groupId>
  <artifactId>concurrent</artifactId>
  <name>concurrent</name>
  <version>1.3.4</version>
  <dependencies/>
</project>

I replaced the contents of this file by that in my local repo.

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>concurrent</groupId>
  <artifactId>concurrent</artifactId>
  <version>1.3.4</version>
</project>

and 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
>     Assignee: Vincent Siveton
>      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


[jira] Commented: (MNG-754) Exception thrown building site

Posted by "Bob Allison (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-754?page=comments#action_44953 ] 

Bob Allison commented on MNG-754:
---------------------------------

I ended up having to rebuild my repository (both my local repository and the one I deploy to).  Now, I cannot duplicate the problem.  My guess is that I had something messed up in one of the repositories and whatever caused that problem has been fixed in SVN already.

> 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


[jira] Commented: (MNG-754) Exception thrown building site

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-754?page=comments#action_45454 ] 

Emmanuel Venisse commented on MNG-754:
--------------------------------------

I fixed concurrent pom

> 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
>     Assignee: Vincent Siveton
>      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


[jira] Commented: (MNG-754) Exception thrown building site

Posted by "Bob Allison (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-754?page=comments#action_44743 ] 

Bob Allison commented on MNG-754:
---------------------------------

I have to take back something I said.  It turns out that the problem does not go away with a POM for the app server's library jar. At least, after clearing my local repository, the problem occurs even with the POM downloaded properly.

> 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


[jira] Closed: (MNG-754) Exception thrown building site

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-754?page=all ]
     
Vincent Siveton closed MNG-754:
-------------------------------

    Resolution: Fixed

Added artifact information in the Exception.
If you can't replicate it, I close it :)

> 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