[
https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293674#comment-13293674
]
angela commented on OAK-138:
----------------------------
+1 for a separate module for the mk-remoting. in my experience the remoting
layers
require quite some additional dependencies that don't make any sense with the
mk implementation. similarly a non-remoting setup should be come with all that
additional stuff...
depending on how big that remoting gets i would even opt for splitting it in 2
separate
modules (client and the server part). for the time being we should at least
make sure that splitting later on was painless.
> 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
