You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Kris Nuttycombe <Kr...@noaa.gov> on 2005/11/01 23:43:35 UTC

[M2] site:site has errors when dependencies are from maven 1 projects

Hi, all,

I'm getting the following error from running mvn site:

java.lang.IllegalArgumentException: Can't find a valid Maven project in
the repository for the artifact [gt2:oracle-spatial:2.0.x-eds].
        at
org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:246)
        at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
        at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:157)
        at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
        at
org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:802)
        at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
        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)

I'm drawing my dependency artifacts from a remote repository that was
built using maven 1.0.2 and has the legacy project layout.
A pom.xml file does exist in my local m2 repository for this artifact,
but that pom appears to be the one from the maven 1.0 repository. I'm
just in the process of beginning to transition my projects to maven 2.0,
so I suspect this will be the case with the vast majority of my artifact
dependencies. How can I work around this problem to get the site to
generate under 2.0?

Thanks,

Kris Nuttycombe

Re: [M2] site:site has errors when dependencies are from maven 1 projects

Posted by Brett Porter <br...@gmail.com>.
This is a bug in the dependency report (I'm not sure if it is fixed
yet - you can file a JIRA if there isn't one already).

You'd need to use <excludeDefaults>true</excludeDefaults> in reporting
to disable the default project-info reports.

 -Brett

On 11/2/05, Kris Nuttycombe <Kr...@noaa.gov> wrote:
> Hi, all,
>
> I'm getting the following error from running mvn site:
>
> java.lang.IllegalArgumentException: Can't find a valid Maven project in
> the repository for the artifact [gt2:oracle-spatial:2.0.x-eds].
>         at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:246)
>         at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
>         at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:157)
>         at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
>         at
> org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:802)
>         at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
>         at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>         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)
>
> I'm drawing my dependency artifacts from a remote repository that was
> built using maven 1.0.2 and has the legacy project layout.
> A pom.xml file does exist in my local m2 repository for this artifact,
> but that pom appears to be the one from the maven 1.0 repository. I'm
> just in the process of beginning to transition my projects to maven 2.0,
> so I suspect this will be the case with the vast majority of my artifact
> dependencies. How can I work around this problem to get the site to
> generate under 2.0?
>
> Thanks,
>
> Kris Nuttycombe
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

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