You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/10/24 11:34:11 UTC

[jira] [Created] (SLING-2627) Provide JCR Wrapper Bundle

Carsten Ziegeler created SLING-2627:
---------------------------------------

             Summary: Provide JCR Wrapper Bundle
                 Key: SLING-2627
                 URL: https://issues.apache.org/jira/browse/SLING-2627
             Project: Sling
          Issue Type: Task
          Components: JCR
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler


As recently discussed in the mailing list, the official jcr api bundle for JCR 2.0 exports all packages as 2.0 although from a semantic versioning point of view 1.1 would have been correct.
Bundles compiling against version 1.0 of the JCR API and using semantic versioning create imports in the 1.x range, excluding 2.0 (and above). Therefore these bundles do not resolve with the JCR 2.0 bundle present.

Therefore we should wrap the JCR api bundle and export the packages in two versions: 1.1 and 2.0

There is http://java.net/jira/browse/JSR_283-810 to fix this in the official bundle. Once this is available we can remove our own wrapper again

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (SLING-2627) Provide JCR Wrapper Bundle

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-2627.
-----------------------------------

    
> Provide JCR Wrapper Bundle
> --------------------------
>
>                 Key: SLING-2627
>                 URL: https://issues.apache.org/jira/browse/SLING-2627
>             Project: Sling
>          Issue Type: Task
>          Components: JCR
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Wrapper 2.0.0
>
>
> As recently discussed in the mailing list, the official jcr api bundle for JCR 2.0 exports all packages as 2.0 although from a semantic versioning point of view 1.1 would have been correct.
> Bundles compiling against version 1.0 of the JCR API and using semantic versioning create imports in the 1.x range, excluding 2.0 (and above). Therefore these bundles do not resolve with the JCR 2.0 bundle present.
> Therefore we should wrap the JCR api bundle and export the packages in two versions: 1.1 and 2.0
> There is http://java.net/jira/browse/JSR_283-810 to fix this in the official bundle. Once this is available we can remove our own wrapper again

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2627) Provide JCR Wrapper Bundle

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2627.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: JCR Wrapper 2.0.0

I decided to use the same version as the jcr api which is wrapped
                
> Provide JCR Wrapper Bundle
> --------------------------
>
>                 Key: SLING-2627
>                 URL: https://issues.apache.org/jira/browse/SLING-2627
>             Project: Sling
>          Issue Type: Task
>          Components: JCR
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Wrapper 2.0.0
>
>
> As recently discussed in the mailing list, the official jcr api bundle for JCR 2.0 exports all packages as 2.0 although from a semantic versioning point of view 1.1 would have been correct.
> Bundles compiling against version 1.0 of the JCR API and using semantic versioning create imports in the 1.x range, excluding 2.0 (and above). Therefore these bundles do not resolve with the JCR 2.0 bundle present.
> Therefore we should wrap the JCR api bundle and export the packages in two versions: 1.1 and 2.0
> There is http://java.net/jira/browse/JSR_283-810 to fix this in the official bundle. Once this is available we can remove our own wrapper again

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira