You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2014/10/13 18:13:33 UTC

[jira] [Updated] (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:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-792:
----------------------------------
    Attachment: 0001-Split-the-bookkeeper-client-from-the-server.patch

Patch renames a lot of files, so I'd like to get it in as soon as possible to avoid a nightmare rebase if other changes go in.

> 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
>             Fix For: 4.4.0
>
>         Attachments: 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.3.4#6332)