If a build fails to complete, and as a result the javadoc is not available, the
JavadocArchiver throws an exception and prints the stack trace to the console.

This is not ideal because it makes the console output hard to decipher. The
build failure appears to have been caused by the Javadoc archiving, when in fact
the failure occurred elsewhere.

Could the JavadocArchiver be changed to only attempt archiving when the build
result is gte UNSTABLE rather than always trying to do it regardless of the
build result?