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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/06/07 11:47:20 UTC

[jira] [Resolved] (OAK-4373) Refactor SegmentTracker

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

Michael Dürig resolved OAK-4373.
--------------------------------
    Resolution: Fixed

The bulk of the work is done with my latest changes. Will report dedicated issues if needed.

> Refactor SegmentTracker
> -----------------------
>
>                 Key: OAK-4373
>                 URL: https://issues.apache.org/jira/browse/OAK-4373
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: technical_debt
>             Fix For: 1.6
>
>
> The {{SegmentTracker}} class has become the dumping ground for everything that wouldn't fit else where. In a personal discussion with [~frm], we figured that this class might be a good starting point refactoring {{segment-tar}} towards better encapsulation. 
> The aim would be to return {{SegmentTracker}} to its initial purpose (i.e. tracking segments) and move all unrelated concerns elsewhere.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)