On 2018-07-24 09:17, Alex Deparvu wrote:
Hi,
Sorry for the mess, I tested this out as best as I could. I would
appreciate to *not* revert the backports, they are needed on that branch.
I can't understand what is breaking here, building 1.8 vs 1.6? how can I
reproduce this locally?
The build works, but the package in 1.6 has now the same version number
as in 1.8, but a different API (due to subsequent changes to the package).
This can be tested by building 1.8 with a baseline comparisonVersiob set
to 1.6.13-SNAPSHOT:
--- snip ---
Index: oak-parent/pom.xml
===================================================================
--- oak-parent/pom.xml (revision 1836528)
+++ oak-parent/pom.xml (working copy)
@@ -187,7 +187,8 @@
<logResults>false</logResults>
<failOnWarning>false</failOnWarning>
<failOnError>true</failOnError>
- <filters>
+ <comparisonVersion>1.6.13-SNAPSHOT</comparisonVersion>
+ <filters>
<!-- Disable baseline for explicitly NOT managed
packages. See OAK-3842 -->
<filter>!org.apache.jackrabbit.oak.spi.blob</filter>
<filter>!org.apache.jackrabbit.oak.spi.blob.split</filter>
--- snip ---
Once we have sorted that out, we should update creating-releases.md
(it's good that Amit spotted the version change!).
Best regards, Julian
