[
https://issues.apache.org/jira/browse/SLING-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833021#action_12833021
]
Carsten Ziegeler commented on SLING-1372:
-----------------------------------------
I think there are two different issues here with jcr api:
- sling's jcr api itself is not tied to any JCR spec api - if we keep the
dependency to JCR 1.0 it is usable with JCR 1.0 and JCR 2.0
- the real problem is that there is no bundled version of the JCR 1.0 api
I think we should keep the dependency in sling's jcr api to JCR 1.0
> Prepare for jrc bundle releases prior to moving to JR2
> ------------------------------------------------------
>
> Key: SLING-1372
> URL: https://issues.apache.org/jira/browse/SLING-1372
> Project: Sling
> Issue Type: Task
> Components: JCR
> Affects Versions: JCR Webdav 2.0.8, JCR Contentloader 2.0.6, JCR
> Jackrabbit Server 2.0.6, JCR Jackrabbit Access Manager 2.0.4, JCR Base
> 2.1.0, JCR API 2.0.8
> Reporter: Ian Boston
> Assignee: Ian Boston
>
> as per http://markmail.org/thread/q7b6m7hoqius62ah
> reverting some commits so we can do a release of before moving to JR2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
