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 2015/08/21 16:40:45 UTC

[jira] [Resolved] (OAK-3050) Move oak-it-osgi to top level

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

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

Fixed at http://svn.apache.org/r1697006

> Move oak-it-osgi to top level 
> ------------------------------
>
>                 Key: OAK-3050
>                 URL: https://issues.apache.org/jira/browse/OAK-3050
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: it
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Minor
>              Labels: modularization, technical_debt
>             Fix For: 1.3.5
>
>
> The {{oak-it}} module only contains the single {{oak-it-osgi}} module, which in turn consists of a single test class. 
> I suggest to at least move {{oak-it-osgi}} to the top level reactor to be consistent with the flat module hierarchy we adopted. IMO an even better solution would be to move the single test class to {{oak-run}}. Not sure whether this is viable though due to the custom assembly necessary. 



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