Hi,
This is due to change 1721196 (associated with JCR-2633), which changes
the persistent data model. Probably the test has just to be tweaked
accordingly, I'll look into it during WE.
Best regards,
Manfred
On 2/12/2016 5:50 PM, Davide Giannella wrote:
On 12/02/2016 16:39, Julian Reschke wrote:
It seems this was caused by switching to Jackrabbit 2.12.0.
Reverting http://svn.apache.org/viewvc?rev=1730031&view=rev might
unblock the release, but of course we'll still need to find out what
Jackrabbit change caused the regression, why that wasn't catched by
Jackrabbit tests, fix that, and make a new Jackrabbit release...
ok. We'll need a stable JR into Oak for 1.4. Honestly I'd rather delay
the 1.3.16 a couple of days for a proper fix so that we'll have longer
coverage in oak with the JR 2.12 branch.
The bug came indeed out after my inclusion of JR 2.12 which highlights
how coupled JR and Oak are; and that with the current approach we need a
reliable continuous build of JR SNAPSHOT and Oak SNAPSHOT to early catch
regressions.
Davide
