[jira] [Updated] (OAK-5834) Remove the deprecated oak-segment module

["Andrei Dulceanu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Dulceanu updated OAK-5834:
---------------------------------
    Attachment: OAK-5834-01.patch

Attaching a patch which addresses the removal of {{oak-segment}} and {{oak-tarmk-standby}} and also the removal of fixtures and ITs pertaining to them. If this is too hard to review, another option would be to do it in a github branch where commits could be easier followed.

This patch doesn't address the changes needed by {{oak-http}} which uses entirely the deprecated API in {{oak-segment}}, nor does it address the changes for {{oak-upgrade}} which will be tracked in a new issue.

[~mduerig], [~frm], could one of you take a look at the patch, please?

> Remove the deprecated oak-segment module
> ----------------------------------------
>
>                 Key: OAK-5834
>                 URL: https://issues.apache.org/jira/browse/OAK-5834
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>              Labels: deprecation, technical_debt
>             Fix For: 1.7.0
>
>         Attachments: OAK-5834-01.patch
>
>
> The {{oak-segment}} module has been deprecated for 1.6 with OAK-4247. We should remove it entirely now:
> * Remove the module
> * Remove fixtures and ITs pertaining to it
> * Remove references from documentation where not needed any more
> An open question is how we should deal with the tooling for {{oak-segment}}. Should we still maintain this in trunk and keep the required classes (which very much might be all) or should we maintain the tooling on the branches? What about new features in tooling? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)