[
https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294366#comment-13294366
]
Dominique Pfister commented on OAK-138:
---------------------------------------
@Thomas: I agree that other MK implementations may benefit from such a
refactoring into at least one project (e.g. oak-mk-commons or oak-mk-base).
Nevertheless, this issue is about moving the remote classes into a separate
project, as oak-mk does not depend on them (opposed to data store, jsop or
cache), so IMHO this is a topic for another issue.
I think Jukka's right about the requirement for a separate MK API project,
therefore:
+1 for oak-mk-remote
+1 for oak-mk-api
> 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
