[
https://issues.apache.org/jira/browse/OAK-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700855#comment-14700855
]
Julian Sedding commented on OAK-3239:
-------------------------------------
I haven't looked at any changes yet. Reading that you want to *port* these
features from RepositoryUpgrade to RepositorySidegrade makes me fear that you
might copy-paste the relevant code.
I believe that most if not all the relevant code is generic enough to allow
re-use without copy-paste. It may require a refactoring, however.
> Port RepositoryUpgrade features to the RepositorySidegrade
> ----------------------------------------------------------
>
> Key: OAK-3239
> URL: https://issues.apache.org/jira/browse/OAK-3239
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: upgrade
> Reporter: Tomek Rękawek
>
> The RepositoryUpgrade class is used to convert CRX2 repository to an Oak node
> store. Recently it gained a lot of features (repeated upgrades, skipping
> orphaned versions, filters, etc.) These features are not available in the
> RepositorySidegrade (used to copy one Oak node store to another one). This is
> a container task for providing the new features to the RepositorySidegrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
