I spent some time on this, there are aspects that I just don't get. Javadoc operates as a report. So it's in the site lifecycle, in a forked execution. So how could it possibly expect to find things in the reactor? Or, is there a provision for that, but somehow the combo of the site plugin and the javadoc plugin fail to ask for it?
Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project gcoref-tools: Could not resolve dependencies for project com.basistech.gcoref:gcoref-tools:jar:2-bim-candidates-SNAPSHOT: Failure to find com.basistech.gcoref:gcoref-core:jar:2-bim-candidates-SNAPSHOT in http://maven.basistech.net/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of Nexus has elapsed or updates are forced at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeForkedExecutions(DefaultLifecycleExecutor.java:173) at org.apache.maven.reporting.exec.DefaultMavenReportExecutor.buildReportPlugin(DefaultMavenReportExecutor.java:282) at org.apache.maven.reporting.exec.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:148) On Fri, Feb 24, 2012 at 3:33 PM, Lukas Theussl <ltheu...@apache.org> wrote: > > > Benson Margulies wrote: >> >> I have a rather vanilla project that fails in release:perform. >> >> The real failure underlying this comes from the following recipe: >> >> 1) Eliminate the result jar artifacts from the local repo. >> >> 2) run mvn install site:site >> >> the site phase fails in javadoc, complaining that one of the modules >> can't find the jar produced by another. >> >> I can reproduce this with 3.0.4. I can probably build up a test case, >> but it's hard for me to believe that this does not result from some >> fairly simple mischief. >> >> Does this ring any bells? > > > one bell ringing here: http://jira.codehaus.org/browse/MSITE-171 > > HTH, > -Lukas > > >> >> The error message when it fails is: >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-site-plugin:3.0:site (default-cli) on >> project gcoref: failed to get report for >> org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal >> on project gcoref-tools: Could not resolve dependencies for project >> com.basistech.gcoref:gcoref-tools:jar:2-bim-candidates-SNAPSHOT: >> Failure to find >> com.basistech.gcoref:gcoref-core:jar:2-bim-candidates-SNAPSHOT in >> http://maven.basistech.net/nexus/content/groups/public was cached in >> the local repository, resolution will not be reattempted until the >> update interval of Nexus has elapsed or updates are forced -> [Help 1] >> >> The reporting section of the top-level effective Pom, which I imagine >> is the most relevant stuff, is : >> >> <reporting> >> >> <outputDirectory>/Users/benson/x/gcoref-tc/target/site</outputDirectory> >> <plugins> >> <plugin> >> <artifactId>maven-site-plugin</artifactId> >> <version>3.0</version> >> <configuration> >> <dependencyDetailsEnabled>false</dependencyDetailsEnabled> >> <dependencyLocationsEnabled>false</dependencyLocationsEnabled> >> </configuration> >> </plugin> >> <plugin> >> <artifactId>maven-project-info-reports-plugin</artifactId> >> <version>2.4</version> >> <reportSets> >> <reportSet> >> <reports> >> <report>summary</report> >> <report>index</report> >> <report>dependencies</report> >> <report>issue-tracking</report> >> <report>scm</report> >> </reports> >> <configuration> >> <dependencyDetailsEnabled>false</dependencyDetailsEnabled> >> >> <dependencyLocationsEnabled>false</dependencyLocationsEnabled> >> </configuration> >> </reportSet> >> </reportSets> >> <configuration> >> <dependencyDetailsEnabled>false</dependencyDetailsEnabled> >> <dependencyLocationsEnabled>false</dependencyLocationsEnabled> >> </configuration> >> </plugin> >> <plugin> >> <artifactId>maven-javadoc-plugin</artifactId> >> <version>2.8</version> >> <reportSets> >> <reportSet> >> <id>html</id> >> <reports> >> <report>javadoc</report> >> </reports> >> <configuration> >> <encoding>utf-8</encoding> >> <attach>true</attach> >> <quiet>true</quiet> >> </configuration> >> </reportSet> >> <reportSet> >> <id>non-aggregate</id> >> <reports> >> <report>javadoc</report> >> </reports> >> <configuration> >> <encoding>utf-8</encoding> >> <attach>true</attach> >> <quiet>true</quiet> >> </configuration> >> </reportSet> >> <reportSet> >> <id>aggregate</id> >> <reports> >> <report>aggregate</report> >> </reports> >> <configuration> >> <encoding>utf-8</encoding> >> <attach>true</attach> >> <quiet>true</quiet> >> </configuration> >> </reportSet> >> </reportSets> >> <configuration> >> <encoding>utf-8</encoding> >> <attach>true</attach> >> <quiet>true</quiet> >> </configuration> >> </plugin> >> </plugins> >> </reporting> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org