[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-168:
--
Fix Version/s: (was: 0.20)
0.19
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
> Fix For: 0.19
>
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-168:
--
Fix Version/s: (was: 1.0)
0.20
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
> Fix For: 0.20
>
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-168:
---
Fix Version/s: (was: 0.17)
1.0
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
> Fix For: 1.0
>
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-168:
-
Fix Version/s: (was: 0.16)
0.17
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
> Fix For: 0.17
>
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-168:
-
Fix Version/s: (was: 0.15)
0.16
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
> Fix For: 0.16
>
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-168:
-
Fix Version/s: (was: 0.14)
0.15
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
> Fix For: 0.15
>
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-168:
--
Fix Version/s: 0.14
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
> Fix For: 0.14
>
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (OAK-168) Basic JCR VersionManager support
[
https://issues.apache.org/jira/browse/OAK-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-168:
-
Issue Type: New Feature (was: Bug)
> Basic JCR VersionManager support
>
>
> Key: OAK-168
> URL: https://issues.apache.org/jira/browse/OAK-168
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
>Reporter: Jukka Zitting
>Assignee: Marcel Reutegger
>
> Versioning is a highly useful feature for many applications, so we definitely
> should support that in Oak.
> We could start by adding a basic JCR VersionManager implementation that
> simply implements checkin operations by copying content from a node to the
> respective version history under {{/jcr:system/jcr:versionStorage}}.
> The next step would then be figuring out whether we want to expose such an
> operation directly in the Oak API, or if a separate versioning plugin and an
> associated validator for changes in the {{/jcr:system/jcr:versionStorage}}
> subtree works better.
> Based on that we can then proceed to implement more of the JCR versioning
> features.
--
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
