Author: chtompki
Date: Wed Apr 18 11:47:12 2018
New Revision: 1829433
URL: http://svn.apache.org/viewvc?rev=1829433&view=rev
Log:
(docs) notes on japicmp
Modified:
commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml
Modified: commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml
URL:
http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml?rev=1829433&r1=1829432&r2=1829433&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml (original)
+++ commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml Wed Apr 18
11:47:12 2018
@@ -208,6 +208,12 @@ mvn -Duser.name=${my_apache_id} -Preleas
presence/absence of appropriate <a
href="http://www.apache.org/legal/src-headers.html";>License Headers</a> in
source files.
</li>
+ <li><strong>Japicmp Report</strong> - reports are only generated
when a jar file has been produced
+ by the build, so <code>mvn clean site</code> will produce an
empty japicmp report, whereas
+ <code>mvn clean package site</code> 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
+ because it does not understand how to properly skip such a
module.
+ </li>
<li><strong>Surefire Report</strong></li>
<li><strong>Javadocs</strong></li>
<li><strong>Source Cross Reference</strong></li>
