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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2017/05/24 13:05:04 UTC
[jira] [Updated] (OAK-5834) Remove the deprecated oak-segment
module
[ https://issues.apache.org/jira/browse/OAK-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella updated OAK-5834:
----------------------------------
Fix Version/s: 1.8
> 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, 1.8
>
> Attachments: OAK-5834-01.patch, OAK-5834-02.patch, OAK-5834-03.patch, OAK-5834-04.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)