Hi --
While working on publishing the kafka 0.8 JAR to our nexus server I noticed
that kafka/project/Build.scala and kafka/project/build/KafkaProject.scala point
to different library versions. In KafkaProject.scala:
def zkClientDep =
<dependency>
<groupId>com.101tec</groupId>
<artifactId>zkclient</artifactId>
<version>0.2</version>
<scope>compile</scope>
</dependency>
def metricsDepsCore =
<dependency>
<groupId>com.yammer.metrics</groupId>
<artifactId>metrics-core</artifactId>
<version>3.0.0-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
def metricsDepsAnnotations =
<dependency>
<groupId>com.yammer.metrics</groupId>
<artifactId>metrics-annotation</artifactId>
<version>3.0.0-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
While Build.scala references different versions (which reside in the local lib
folder):
// POM Tweaking for core:
def zkClientDep =
<dependency>
<groupId>zkclient</groupId>
<artifactId>zkclient</artifactId>
<version>20120522</version>
<scope>compile</scope>
</dependency>
def metricsDeps =
<dependencies>
<dependency>
<groupId>com.yammer.metrics</groupId>
<artifactId>metrics-core</artifactId>
<version>3.0.0-c0c8be71</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.yammer.metrics</groupId>
<artifactId>metrics-annotations</artifactId>
<version>3.0.0-c0c8be71</version>
<scope>compile</scope>
</dependency>
</dependencies>
As there seem to be API differences between these different versions I am
wondering whether the different references are by design or they're something
that slipped through the cracks. Has anybody else ran into this?
Thanks,
-Dragos