On 5/31/17 3:52 PM, Julian Hyde wrote:
On May 30, 2017, at 2:37 PM, Josh Elser wrote:
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.
Thanks, I’ll try that
> On May 30, 2017, at 2:37 PM, Josh Elser wrote:
>
> 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.
Thanks, I’ll try that next time.
By the way, I tried t
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
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: Coul
