[
https://issues.apache.org/jira/browse/SLING-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833022#action_12833022
]
Justin Edelson commented on SLING-1372:
---------------------------------------
> I think we should keep the dependency in sling's jcr api to JCR 1.0
agreed
What I mean by "They don't have any dependency on JCR 2, but jcr.api > 2.0.4 is
unusable without the JCR 2 API bundle" was really "They don't have any
dependency on JCR 2, but jcr.api > 2.0.4 is unusable without *a bundle which
exports the JCR (1 or 2) API*".
> 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.
