You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Manfred Baedke (JIRA)" <ji...@apache.org> on 2015/04/09 15:58:12 UTC
[jira] [Comment Edited] (OAK-2737) RepositoryUpgrade.copy() should
allow custom commit hooks
[ https://issues.apache.org/jira/browse/OAK-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487364#comment-14487364 ]
Manfred Baedke edited comment on OAK-2737 at 4/9/15 1:57 PM:
-------------------------------------------------------------
Solved in trunk with r1672350, in 1.0 with r1672355.
was (Author: baedke):
Solved in trunk with r1672350.
> RepositoryUpgrade.copy() should allow custom commit hooks
> ---------------------------------------------------------
>
> Key: OAK-2737
> URL: https://issues.apache.org/jira/browse/OAK-2737
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
> Affects Versions: 1.0.12, 1.1.8
> Reporter: Manfred Baedke
> Assignee: Manfred Baedke
> Priority: Minor
> Fix For: 1.0.13, 1.2.1
>
>
> Custom commit hooks will allow content transformation during the upgrade process. For example, one might want to migrate a custom JAAS login module to an ExternalLoginModule as featured by Oak, which requires certain properties to be set that are not available on the source repository.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)