[
https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293787#comment-13293787
]
Jukka Zitting commented on OAK-138:
-----------------------------------
> oak-mk contains one specific implementation of the MicroKernel API.
It also contains the MicroKernel API itself. As long as we don't want to split
the API to a separate component, things like remoting IMHO fit best within that
same component. Otherwise we have the troublesome situation where the remoting
component depends on this specific implementation of the API. If we avoid the
separate component, we only need to deal with package-level dependencies, where
something like the .mk.server -> .mk.api dependency is perfectly fine.
> 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
