You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/22 15:11:20 UTC

[jira] [Commented] (SLING-5891) Make oak restrictions compatible to oak > 1.2

    [ https://issues.apache.org/jira/browse/SLING-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389657#comment-15389657 ] 

ASF GitHub Bot commented on SLING-5891:
---------------------------------------

GitHub user ghenzler opened a pull request:

    https://github.com/apache/sling/pull/158

    SLING-5891 Provide compatibility for oak 1.2-1.5

    
    Sorry for the formatting noise  (now it is all spaces). 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ghenzler/sling SLING-5891-oak14-compatibility

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/158.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #158
    
----
commit 165cafb1d3ce907718d2136a148eb545033b2ecf
Author: georg.henzler <ge...@netcentric.biz>
Date:   2016-07-22T15:03:14Z

    SLING-5891 Provide compatibility for oak 1.2-1.5

----


> Make oak restrictions compatible to oak > 1.2
> ---------------------------------------------
>
>                 Key: SLING-5891
>                 URL: https://issues.apache.org/jira/browse/SLING-5891
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Georg Henzler
>            Assignee: Robert Munteanu
>
> The initial version was tested with oak-core v1.2.7, however some users might want to use it with more recent versions (especially 1.4.x). 
> The problematic packages are {{org.apache.jackrabbit.oak.api}} and {{org.apache.jackrabbit.oak.util}}. Usually it is not a good idea to tweak package imports manually, but I think for this particular case there is no other solution to provide compatibility across oak versions. The functionality that is actually used from those two packages is also very basic (Tree, Type, PropertyState and TreeUtil), therefore providing a version range for them is not problematic IMHO.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)