[
https://issues.apache.org/jira/browse/KAFKA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636127#comment-13636127
]
Esko Suomi commented on KAFKA-865:
----------------------------------
I guess I should point out that when it comes to dependencies, SBT is a
bastardization of Ivy which on its own works really nice with Maven
repositories, among other things.
I do agree with several points here, especially the point about separating the
server and client. As an example in our case we have to treat servers as really
slowly evolving creatures and most of the bugs we've hit during our period of
running Kafka have been exclusively client bugs. Because the two are tightly
coupled, all we can do is to wait for the next release. If these two were
separated, we could've remedied those client bugs with a quick update since the
actual software we have can be updated as often as we like.
> Mavenize and separate the client.
> ---------------------------------
>
> Key: KAFKA-865
> URL: https://issues.apache.org/jira/browse/KAFKA-865
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 0.8
> Reporter: Ashwanth Fernando
>
> It seems that the java client for Kafka is also bundled with the server JAR
> file and this is generated using sbt package. This is difficult for java
> folks to work with because:
> 1) Many java shops use maven (and a lot of them have a Sonatype Nexus
> repository in house) for dependency management. They want to specify the GAV
> and bang, the client jar and all its dependencies should be added to the
> application's classpath. I can't do that right now, because I need to run
> ./sbt eclipse, get the .JAR, add that to my classpath, add a whole lot of
> dependencies (log4j, slf4j, zkClient and so on) manually, which is a pain.
> There are 90 million maven central uploads/downloads in 2012 alone. Almost
> all the java shops out there have maven (either central or in house sonatype).
> 2) Separation of concerns - keeping the server (core) and the client's
> classes increases the size of the bundle for the client and also everytime
> the server's code changes and a release is performed, the client also needs
> to update their .JAR file. which is not very great. We don't want a ton of
> clients to update their .JAR file, just because a faster replication strategy
> for my kafka cluster changed in a new release.
> Action items are to separate the client portion of Kafka, add it in a pom
> along with the compile time dependencies and upload it to Maven Central or if
> you have a LinkedIn externally exposed Nexus, over there.
> This will increase adoption of the Kafka framework.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
