sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] JEBailey commented on a change in pull request #1: Sling 3270
Date Thu, 10 Jan 2019 15:55:13 GMT
JEBailey commented on a change in pull request #1: Sling 3270

 File path: pom.xml
 @@ -37,25 +37,36 @@
-        <org.ops4j.pax.exam.version>4.11.0</org.ops4j.pax.exam.version>
+        <org.ops4j.pax.exam.version>4.12.0</org.ops4j.pax.exam.version>
+        <>UTF-8</>
+        <project.resources.sourceEncoding>UTF-8</project.resources.sourceEncoding>
-      <tag>HEAD</tag>
-  </scm>
+        <tag>HEAD</tag>
+    </scm>
-                <groupId>biz.aQute.bnd</groupId>
-                <artifactId>bnd-maven-plugin</artifactId>
 Review comment:
   @kwin  I misunderstood, from my experience between the two it feels like the bnd-maven-plugin
is the step back. However to answer your question. Of the multiple concerns that I encountered,
the specific problem is that the baselining is ignoring the 
   when I use bnd-maven-plugin I get the following
   [INFO] --- bnd-baseline-maven-plugin:3.5.0:baseline (default) @
   [INFO] Automatically determining the baseline version for
using repositories [apache.snapshots.https (,
default, releases+snapshots), central (,
default, releases), snapshots (,
default, releases+snapshots), apache.snapshots (, default,
   [INFO] The baseline version was found to be 1.0.2
   [ERROR] The bundle version change (1.0.2 to 1.0.3) is too low, the new version must be
at least 1.1.0
   It's obtaining the versioning information from the bundle instead of the package-info.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message