[
https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293666#comment-13293666
]
Stefan Guggisberg commented on OAK-138:
---------------------------------------
> I'd rather just put the code to oak-mk as it's tightly bound to the
> MicroKernel interface.
oak-mk contains one specific implementation of the MicroKernel API.
the remoting code OTOH is generic and can be used with any mk implementation.
i'd prefer a separate module for the remoting layer instead of putting
everything mk-related into the current oak-mk module.
> Move client/server package in oak-mk to separate project
> --------------------------------------------------------
>
> Key: OAK-138
> URL: https://issues.apache.org/jira/browse/OAK-138
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, it, mk, run
> Affects Versions: 0.3
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
>
> As a further cleanup step in OAK-13, I'd like to move the packages
> o.a.j.mk.client and o.a.j.mk.server and referenced classes in oak-mk to a
> separate project, e.g. oak-mk-remote.
> This new project will then be added as a dependency to:
> oak-core
> oak-run
> oak-it-mk
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
