On Mon, 2015-06-22 at 19:58 -0500, Carsten Ziegeler wrote: > Am 22.06.15 um 09:14 schrieb Robert Munteanu: > > On Mon, 2015-06-22 at 15:26 +0200, Bertrand Delacretaz wrote: > > > Hi, > > > > > > We solved 5 issues in this release: > > > http://s.apache.org/UEG > > > > Sorry for coming in so late with a comment, but I saw that the fix > > for > > SLING-4820 [1] upgraded the oak dependency to 1.3.0 [2]. With the > > latest version the following oak-related imports are generated: > > > > org.apache.jackrabbit.oak.plugins.observation;resolution:=optional > > ;ver > > sion="[2.0,3)" > > org.apache.jackrabbit.oak.spi.commit;resolution:=optional;version= > > "[1. > > 0,2)" > > > > If I understand things correctly, for Oak 1.3.0+ both imports will > > be > > satisfied, but for older versions only the second one will be. > > Which > > means that for Oak 1.2.x ( what we currently use in the launchpad ) > > we > > won't benefit from the improved support. > > > > Could this be re-done with a manual import-dependency range, > > something > > like > > > > > > org.apache.jackrabbit.oak.plugins.observation;version="[1.0,3.0)";r > > esol > > ution:=optional > > > > ? It would allow wiring dependencies against older versions of Oak > > as > > far as I can tell. > > Not sure if we should go this way as it sounds dangerous to me. Fact > is > we haven't released any Sling version with Oak yet. So we should > rather > got with 1.3 in Sling and in this case the resource resolver module > works fine. > If someone wants to use that on an older Oak version, he can easily > patch the manifest for that particular use case.
OK, works for me. I'll update Oak to 1.3.0 in the launchpad, to make sure we don't get any unexpected results. Robert
