site:site fails due to not resolving in the reactor?
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? 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 artifactIdmaven-site-plugin/artifactId version3.0/version configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-project-info-reports-plugin/artifactId version2.4/version reportSets reportSet reports reportsummary/report reportindex/report reportdependencies/report reportissue-tracking/report reportscm/report /reports configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /reportSet /reportSets configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.8/version reportSets reportSet idhtml/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idnon-aggregate/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idaggregate/id reports reportaggregate/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet /reportSets configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /plugin /plugins /reporting - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site:site fails due to not resolving in the reactor?
If I eliminate checkstyle and pmd from my pom (not just skip them), this changes to: This dependency has been excluded from the Javadoc classpath. You should rerun javadoc after executing mvn install. [WARNING] IGNORED to add some artifacts in the classpath. See above. Downloading: http://maven.basistech.net/nexus/content/groups/public/com/basistech/gcoref/gcoref-tools/2-bim-candidates-SNAPSHOT/maven-metadata.xml Downloading: http://maven.basistech.net/nexus/content/groups/public/com/basistech/gcoref/gcoref-tools/2-bim-candidates-SNAPSHOT/gcoref-tools-2-bim-candidates-SNAPSHOT.jar [WARNING] The dependency: [com.basistech.gcoref:gcoref-core:jar:2-bim-candidates-SNAPSHOT] can't be resolved but has been found in the reactor (probably snapshots). This dependency has been excluded from the Javadoc classpath. You should rerun javadoc after executing mvn install. [WARNING] The dependency: [com.basistech.gcoref:gcoref-tools:jar:2-bim-candidates-SNAPSHOT] can't be resolved but has been found in the reactor (probably snapshots). This dependency has been excluded from the Javadoc classpath. You should rerun javadoc after executing mvn install. [WARNING] IGNORED to add some artifacts in the classpath. See above. On Fri, Feb 24, 2012 at 2:22 PM, Benson Margulies bimargul...@gmail.com 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? 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 artifactIdmaven-site-plugin/artifactId version3.0/version configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-project-info-reports-plugin/artifactId version2.4/version reportSets reportSet reports reportsummary/report reportindex/report reportdependencies/report reportissue-tracking/report reportscm/report /reports configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /reportSet /reportSets configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.8/version reportSets reportSet idhtml/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idnon-aggregate/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idaggregate/id reports reportaggregate/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet /reportSets configuration
Re: site:site fails due to not resolving in the reactor?
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 artifactIdmaven-site-plugin/artifactId version3.0/version configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-project-info-reports-plugin/artifactId version2.4/version reportSets reportSet reports reportsummary/report reportindex/report reportdependencies/report reportissue-tracking/report reportscm/report /reports configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /reportSet /reportSets configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.8/version reportSets reportSet idhtml/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idnon-aggregate/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idaggregate/id reports reportaggregate/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet /reportSets configuration encodingutf-8/encoding attachtrue/attach quiettrue/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
Re: site:site fails due to not resolving in the reactor?
Sure enough. 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 artifactIdmaven-site-plugin/artifactId version3.0/version configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-project-info-reports-plugin/artifactId version2.4/version reportSets reportSet reports reportsummary/report reportindex/report reportdependencies/report reportissue-tracking/report reportscm/report /reports configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /reportSet /reportSets configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.8/version reportSets reportSet idhtml/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idnon-aggregate/id reports reportjavadoc/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet reportSet idaggregate/id reports reportaggregate/report /reports configuration encodingutf-8/encoding attachtrue/attach quiettrue/quiet /configuration /reportSet /reportSets configuration encodingutf-8/encoding attachtrue/attach quiettrue/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
