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-3862) Move integration tests in a different Maven module
Date Mon, 18 Jan 2016 17:40:39 GMT

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

Michael Dürig commented on OAK-3862:
------------------------------------

+1

> Move integration tests in a different Maven module
> --------------------------------------------------
>
>                 Key: OAK-3862
>                 URL: https://issues.apache.org/jira/browse/OAK-3862
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>             Fix For: 1.4
>
>
> While moving the Segment Store and related packages into its own bundle, I figured out
that integration tests contained in {{oak-core}} contribute to a cyclic dependency between
the (new) {{oak-segment}} bundle and {{oak-core}}.
> The dependency is due to the usage of {{NodeStoreFixture}} to instantiate different implementations
of {{NodeStore}} in a semi-transparent way.
> Tests depending on {{NodeStoreFixture}} are most likely integration tests. A clean solution
to this problem would be to move those integration tests into a new Maven module, referencing
the API and implementation modules as needed.



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

Mime
View raw message