[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289231#comment-14289231
]
ASF GitHub Bot commented on SLING-4318:
---------------------------------------
GitHub user trekawek opened a pull request:
https://github.com/apache/sling/pull/59
SLING-4318 :restore operation for the SlingPostServlet
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trekawek/sling SLING-4318-restore-operation
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/59.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 #59
----
commit a1aa27f32671bbe4f9968b38e79eb721ffba1f8e
Author: Tomasz Rękawek <[email protected]>
Date: 2015-01-23T13:21:53Z
Initial version of the :restore operation.
----
> 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)