jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project
Date Wed, 13 Jun 2012 12:01:44 GMT

    [ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294393#comment-13294393
] 

Thomas Mueller commented on OAK-138:
------------------------------------

I understand this issue is about remoting. However, we should be consistent about when we
create separate projects. So if we create separate projects for remoting and the MK API, then
we should also create separate projects for many other components. The large project list
above was only half joking - it was just the logical conclusion if we apply the same reasoning
for separating the remoting implementation to other components. I personally don't want to
go down that path, but if everybody agrees we need separate projects for things like the MK
API, remoting (possibly multiple projects: client, server, commons), the log wrapper, then
we would also separate projects for the data store (as it can be used in other MK implementations),
and so on.

> alternative mk implementations require an explicit dependency on the 'default' implementation
in oak-mk, including all transitive dependencies such as h2 etc. i find that weird.

Alternative MK implementations may want to re-use part of the data store implementation (the
AbstractBlobStore, possibly the FileBlobStore and MemoryBlobStore). Therefore, for the same
reason, the data store would need to be moved to a different project.

An alternative is to reduce the dependencies, for example make the dependency to H2 test only.
It looks like the dependency is currently needed because the JdbcConnectionPool is used. Possibly
we don't really need a connection pool (?) - in that case the dependency would not be needed.

                
> 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

        

Mime
View raw message