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 2016/05/16 13:58:18 UTC
[jira] [Closed] (OAK-4259) Implement fixtures for running again
oak-segment and/or oak-segment-next
[ https://issues.apache.org/jira/browse/OAK-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella closed OAK-4259.
---------------------------------
Bulk close for 1.5.2
> Implement fixtures for running again oak-segment and/or oak-segment-next
> ------------------------------------------------------------------------
>
> Key: OAK-4259
> URL: https://issues.apache.org/jira/browse/OAK-4259
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Francesco Mari
> Priority: Blocker
> Labels: testing
> Fix For: 1.6, 1.5.2
>
>
> We need fixtures to run UTs / ITs against either or both segment implementations {{oak-segment}} and {{oak-segment-next}}.
> Ideally we can enable them individually through e.g. environment variables. A standard build would run against {{oak-segment}} so not to affect others. {{oak-segment-next}} could be enabled on request locally or for the CI.
> Once we deprecate {{oak-segment}} we would switch the default fixture to {{oak-segment-next}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)