It should - yes. So that would in theory unblock KAFKA-133 right?
The only reason we needed the hand-built metrics jar is because of some CSV
reporter fixes in 3.* which is required for the system testing framework.
I'm sure it is possible but don't know sbt enough to spend time on this: we
can have a custom package task that uses the custom jars and the regular
package task can use 2.2.0.


On Tue, Nov 27, 2012 at 1:33 PM, Jason Rosenberg <j...@squareup.com> wrote:

> so, will yammer 2.2.0 work with kafka 0.8?
>
> On Tue, Nov 27, 2012 at 1:10 PM, Otis Gospodnetic <
> otis_gospodne...@yahoo.com> wrote:
>
> > Hi Jason,
> >
> > See https://issues.apache.org/jira/browse/KAFKA-133 for info about:
> >
> > * zkclient (0.2 is on the way to Sonatype)
> > * yammer metrics (note: 2.2.0 was just released actually and going to
> > Maven Central)
> >
> > Otis
> > ----
> > Performance Monitoring for Solr / ElasticSearch / HBase -
> > http://sematext.com/spm
> >
> >
> >
> > >________________________________
> > > From: Jason Rosenberg <j...@squareup.com>
> > >To: kafka-users@incubator.apache.org
> > >Sent: Monday, November 26, 2012 8:29 PM
> > >Subject: 0.8 dependencies (and maven)
> > >
> > >I just checked out the latest 0.8 branch, and ran ./sbt make-pom.
> > >
> > >I notice that some of the dependencies generated are either not released
> > >versions, e.g.:
> > >
> > >         <dependency>
> > >                <groupId>com.yammer.metrics</groupId>
> > >                <artifactId>metrics-core</artifactId>
> > >                <version>3.0.0-c0c8be71</version>
> > >                <scope>compile</scope>
> > >         </dependency>
> > >
> > >Latest yammer release is 2.1.5......Is there a specific reason why a
> > >non-released version of yammer metrics is needed?  I worry it will make
> it
> > >difficult to live in app container that is using the 2.1.x version of
> > >yammer.
> > >
> > >and:
> > >
> > >         <dependency>
> > >            <groupId>zkclient</groupId>
> > >            <artifactId>zkclient</artifactId>
> > >            <version>20120522</version>
> > >            <scope>compile</scope>
> > >        </dependency>
> > >
> > >Is this very specific version required?
> > >
> > >And then there's also this:
> > >
> > >        <dependency>
> > >            <groupId>org.slf4j</groupId>
> > >            <artifactId>slf4j-simple</artifactId>
> > >            <version>latest.release</version>
> > >            <scope>compile</scope>
> > >        </dependency>
> > >
> > >Can we have an actual version, please?  (previous versions of kafka
> didn't
> > >use slf4j, is it required here?)
> > >
> > >Also, the generated pom is also missing the scala language library, as
> in
> > >previous versions of kafka, so I've been adding this:
> > >
> > ><dependency>
> > ><groupId>org.scala-lang</groupId>
> > ><artifactId>scala-library</artifactId>
> > ><version>2.8.0</version>
> > ></dependency>
> > >
> > >Can we have make-pom include this by default (otherwise it's not
> possible
> > >to use much of the kafka library from client code).
> > >
> > >Jason
> > >
> > >
> > >
> >
>

Reply via email to