In the case of https://issues.apache.org/jira/browse/SLING-4820 <https://issues.apache.org/jira/browse/SLING-4820> there is no simple solution to support both Oak 1.2 and 1.3. Since Oak incremented the major version of the package (although at first glance the used interfaces from https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/observation/NodeObserver.java <https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/observation/NodeObserver.java> look like they haven’t been changed), the only solution would be to increase the version range of the Import-Package statement within the JCR Resource bundle manually to cover both 1.0 and 2.0. But this looks really like a hack and is IMHO too dangerous, as it may lead to not-running bundles although all dependencies could be resolved. This is exactly what we want to prevent with semantic versioning. Konrad
> On 15 Sep 2015, at 11:22, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > > Hi, > > On Tue, Sep 15, 2015 at 9:26 AM, Konrad Windszus <konra...@gmx.de> wrote: >> ...What is the policy of supporting Oak 1.2 in Sling?... > > I don't think we have a defined policy so far - in general I like our > tests to run against the latest Oak to stay on top of things, but > you're right that it makes sense to also support the latest stable > version. > > Do you know what changes are needed for that? > > -Bertrand
