Author: buildbot
Date: Wed Apr 18 11:50:50 2018
New Revision: 1028607
Log:
Staging update by buildbot for commons
Modified:
websites/staging/commons/trunk/content/ (props changed)
websites/staging/commons/trunk/content/commons-parent-pom.html
Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr 18 11:50:50 2018
@@ -1 +1 @@
-1829433
+1829434
Modified: websites/staging/commons/trunk/content/commons-parent-pom.html
==============================================================================
--- websites/staging/commons/trunk/content/commons-parent-pom.html (original)
+++ websites/staging/commons/trunk/content/commons-parent-pom.html Wed Apr 18
11:50:50 2018
@@ -479,7 +479,7 @@ mvn -Duser.name=${my_apache_id} -Preleas
source files.
</li>
-<li><b>Japicmp Report</b> - reports are only generated when a jar file has
been produced
+<li><b><a class="externalLink"
href="https://siom79.github.io/japicmp/";>Japicmp</a> Report</b> - reports are
only generated when a jar file has been produced
by the build, so <tt>mvn clean site</tt> will produce an
empty japicmp report, whereas
<tt>mvn clean package site</tt> will produce a full report.
Furthermore, in building pom
only modules, japicmp has a tendency to print out a
stacktrace under the pretense of a warning
