jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-5834) Remove the deprecated oak-segment module
Date Wed, 01 Mar 2017 16:56:45 GMT

    [ https://issues.apache.org/jira/browse/OAK-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890542#comment-15890542

Michael Dürig commented on OAK-5834:

Looks good. There is more code affected that I would have imagined. Good we are getting this

* Removal of {{FileStoreRevisionRecover}}: I think we need this again for Segment Tar. Please
create a follow up issue.
* Removal of {{RepositoryGrowthTest}}: Please clarify with [~chetanm] whether we still need

> 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

View raw message