Author: chtompki
Date: Tue Apr 10 12:15:18 2018
New Revision: 1828807

Adding stacktrace to RELEASE-NOTES.txt notes


Modified: commons/proper/commons-parent/trunk/RELEASE-NOTES.txt
--- commons/proper/commons-parent/trunk/RELEASE-NOTES.txt (original)
+++ commons/proper/commons-parent/trunk/RELEASE-NOTES.txt Tue Apr 10 12:15:18 
@@ -14,7 +14,28 @@ Notes on japicmp usage in 46
 For japicmp to work when running 'mvn site', we must first run package
 because japicmp needs a built artifact to which to compare the previous
 version. Thus, we run 'mvn package site' to get an appropriate japicmp
+report. Further, during project build we see the following warning and
+stacktrace during site generation:
+[debug] No packaging support defined, no filtering
+[info] Skipping execution because packaging of this module is 'pom'.
+[debug] Searching for versions in versionRange: (,46)
+[info] Unable to find a previous version of the project in the repository.
+[warn] No new version specified and file '/..../commons-parent/pom.xml' of 
artifact could not be opened as jar archive: error in opening zip file
+ error in opening zip file
+        at Method)
+        at<init>(
+        at<init>(
+        at java.util.jar.JarFile.<init>(
+        at java.util.jar.JarFile.<init>(
+        at 
+        at japicmp.maven.JApiCmpMojo.getOptions(
+        at japicmp.maven.JApiCmpReport.getOptions(
+        at japicmp.maven.JApiCmpReport.getDescription(
+        at
 Changes in this version include:

Reply via email to