Hi, Grant, Thanks for the email. Yes, we should try to keep up with the latest stable version of the dependencies. We want to be a bit careful with api compatibilities for dependencies used in the clients. Incompatible changes make the upgrade of the clients painful. For example, metrics-core wasn't very careful with compatibility in a release a couple yeas ago.
This is probably too late for the 0.9.0.0 release since we won't have enough time to test this thoroughly. I recommend that we do that in trunk. Thanks, Jun On Tue, Nov 10, 2015 at 8:12 AM, Grant Henke <ghe...@cloudera.com> wrote: > With a new major release comes the opportunity to update dependencies; > potentially including bug fixes, performance improvements, and useful > features. Below is some analysis of the current state of Kafka dependencies > and the available updates with change logs: > > Note: this shows [Current -> Newest], there may be maintenance release in > between that are a more appropriate choice. > > > - org.scala-lang:scala-library [2.10.5 -> 2.10.6] > - http://www.scala-lang.org/news/2.10.6 > - Scala 2.10.6 resolves a license incompatibility in > scala.util.Sorting > - Otherwise identical to Scala 2.10.5 > - Requires small gradle build changes and variable in > kafka-run-class.sh > - org.xerial.snappy:snappy-java [1.1.1.7 -> 1.1.2] > - https://github.com/xerial/snappy-java/blob/develop/Milestone.md > - Fixes SnappyOutputStream.close() is not idempotent > - net.jpountz.lz4:lz4 [1.2.0 -> 1.3] > - http://blog.jpountz.net/post/103674111856/lz4-java-130-is-out > - May want to rewrite integration to use bytebuffers now that its > available > - junit:junit [4.11 -> 4.12] > - > > https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.12.md > - org.easymock:easymock [3.3.1 -> 3.4] > - https://github.com/easymock/easymock/releases/tag/easymock-3.4 > - org.powermock:powermock-api-easymock [1.6.2 -> 1.6.3] > - org.powermock:powermock-module-junit4 [1.6.2 -> 1.6.3] > - https://github.com/jayway/powermock/blob/master/changelog.txt > - org.slf4j:slf4j-api [1.7.6 -> 1.7.12] > - org.slf4j:slf4j-log4j12 [1.7.6 -> 1.7.12 > - http://www.slf4j.org/news.html > - com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider [2.5.4 -> > 2.6.3] > - > > https://github.com/FasterXML/jackson-jaxrs-providers/blob/master/release-notes/VERSION > - com.fasterxml.jackson.core:jackson-databind [2.5.4 -> 2.6.3] > - > > https://github.com/FasterXML/jackson-databind/blob/master/release-notes/VERSION#L61 > - many small bug fixes > - org.eclipse.jetty:jetty-server [9.2.12.v20150709 -> 9.3.5.v20151012] > - org.eclipse.jetty:jetty-servlet [9.2.12.v20150709 -> 9.3.5.v20151012] > - https://github.com/eclipse/jetty.project/blob/master/VERSION.txt > - org.bouncycastle:bcpkix-jdk15on [1.52 -> 1.53] > - https://www.bouncycastle.org/releasenotes.html > - net.sf.jopt-simple:jopt-simple [3.2 -> 4.9] > - Only used in migration tool > - Remove in favor of argparse? to reduce dependencies > - org.rocksdb:rocksdbjni [3.10.1 -> 4.0] > - https://github.com/facebook/rocksdb/releases > - org.objenesis:objenesis [1.2 -> 2.2] > - http://objenesis.org/notes.html > - Is this library still needed/used? > - com.yammer.metrics:metrics-core [2.2.0 -> NA] > - Under new location: io.dropwizard.metrics:metrics-core:3.1.2 > - Explanation: > > https://groups.google.com/d/msg/dropwizard-user/1usH7frpnZE/RSQUsOBFMsoJ > - Likely to big of a change to be worth it, since Kafka metrics now > exists > - Listed for completeness > > So do we want to update any of these? Any that we absolutely should not? > Once we get a list of those to be updated I can send a pull request. > > Thanks, > Grant > -- > Grant Henke > Software Engineer | Cloudera > gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke >
