Return-Path: X-Original-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 93DD6C1A5 for ; Tue, 12 Jun 2012 17:26:43 +0000 (UTC) Received: (qmail 27486 invoked by uid 500); 12 Jun 2012 17:26:43 -0000 Delivered-To: apmail-jackrabbit-oak-dev-archive@jackrabbit.apache.org Received: (qmail 27411 invoked by uid 500); 12 Jun 2012 17:26:43 -0000 Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-dev@jackrabbit.apache.org Received: (qmail 27385 invoked by uid 99); 12 Jun 2012 17:26:43 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jun 2012 17:26:43 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id E46961404B4 for ; Tue, 12 Jun 2012 17:26:42 +0000 (UTC) Date: Tue, 12 Jun 2012 17:26:42 +0000 (UTC) From: "Jukka Zitting (JIRA)" To: oak-dev@jackrabbit.apache.org Message-ID: <948602658.8508.1339522002937.JavaMail.jiratomcat@issues-vm> In-Reply-To: <933135886.6735.1339493983865.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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