You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2017/10/17 21:30:02 UTC

[jira] [Commented] (BOOKKEEPER-792) Split bookkeeper client into a separate maven module

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

Ivan Kelly commented on BOOKKEEPER-792:
---------------------------------------

Migrated to github https://github.com/apache/bookkeeper/issues/617

> Split bookkeeper client into a separate maven module
> ----------------------------------------------------
>
>                 Key: BOOKKEEPER-792
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-792
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>              Labels: ghmigrated, iktriage0
>             Fix For: 4.6.0
>
>         Attachments: 0001-Split-the-bookkeeper-client-from-the-server.patch, 0001-Split-the-bookkeeper-client-from-the-server.patch, 0001-Split-the-bookkeeper-client-from-the-server.patch
>
>
> Right now, to include bookkeeper as a dependency, you need to include org.apache.bookkeeper:bookkeeper-server
> This pulls in all the bookkeeper-server code, and all the server dependencies as well as the client. The server dependencies are larger than the client dependencies. For one thing, it pulls in jna and log4j which should never be pulled in from the client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)