Probably a result of the Maven reactor being 'weird'.
If you do a `mvn site` alone, the reactor isn't going to build JARs for the other modules (such as core). The `site` target does _not_ imply a `package` (unlike verify implying package or package implying compile, etc). As such, the reactor doesn't know about the SNAPSHOT jars from the other modules in the project. Maven's only other option at this point is to pull from the remote.
In your case, Jenkins hasn't yet (it has now[1]) published snapshot builds for 1.11.0-SNAPSHOT. So, it doesn't pick up avatica-core from the reactor and it can't get it from the remote, so it fails to you.
I believe the solution for this in the future is to do something like `mvn package site -DskipTests -Dcheckstyle.skip` until the first SNAPSHOT after a release is built by Jenkins.
[1] https://repository.apache.org/content/groups/snapshots/org/apache/calcite/avatica/avatica-core/
On 5/30/17 4:01 PM, Julian Hyde wrote:
Anyone have an idea why "mvn site" is failing? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project avatica-parent: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal on project avatica-core: Could not resolve dependencies for project org.apache.calcite.avatica:avatica-core:jar:1.11.0-SNAPSHOT: Failure to find org.apache.calcite.avatica:avatica-metrics:jar:1.11.0-SNAPSHOT in https://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced -> [Help 1]
