[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282811#comment-14282811
]
Bruce Edge commented on SLING-4318:
-----------------------------------
After re-reading the activities vs labels docs in the JCS 2.0 spec, I agree,
there's no need for activities in the sling versioning API as their intended
use is as a merge scope handle.
My original thought was that an activity would be a mechanism to obtain the
difference between version labels thereby negating the need for the client to
calculate the set of changes between labels.
> Sling resource API does not expose any versioning features - bounty offered.
> ----------------------------------------------------------------------------
>
> Key: SLING-4318
> URL: https://issues.apache.org/jira/browse/SLING-4318
> Project: Sling
> Issue Type: New Feature
> Components: Documentation, JCR, Servlets
> Affects Versions: Servlets Resolver 2.3.8
> Environment: N/A
> Reporter: Bruce Edge
> Labels: api, crud, servlet-api, versioning, versions
>
> The javax.jcr.version.VersionManager is not exposed in the sling resource API:
> http://thread.gmane.org/gmane.comp.apache.sling.user/1610
> My company is interested in paying for this development. Please contact if
> interested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
