Eh, correction: I see KAFKA-133 is actually *not* marked for 0.8 release - it's just marked as affecting the 0.8 release. :(
Otis ---- Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm >________________________________ > From: Otis Gospodnetic <otis_gospodne...@yahoo.com> >To: "kafka-users@incubator.apache.org" <kafka-users@incubator.apache.org> >Sent: Tuesday, November 20, 2012 9:40 PM >Subject: Re: Kafka + Maven > >Pretty pretty pretty please please please from us at Sematext, too. I >provided the instructions in KAFKA-133: > >https://issues.apache.org/jira/browse/KAFKA-133?focusedCommentId=13500822&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13500822 > > >I've also pinged zkclient keepers and asked them to publish zkclient 0.2, so >Kafka can reference it instead of having a local copy of it. > >KAFKA-133 is now marked for 0.8, great! > >Otis >---- > >Performance Monitoring for Solr / ElasticSearch / HBase - >http://sematext.com/spm > > > >>________________________________ >> From: Brian O'Neill <b...@alumni.brown.edu> >>To: kafka-users@incubator.apache.org >>Sent: Tuesday, November 20, 2012 7:19 PM >>Subject: Re: Kafka + Maven >> >>+1, pretty please, please, please. >>(we also use Storm, and would love to see published artifacts) >> >>We use sonatype to publish our open source artifacts: >>https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide >> >>Its fairly straightforward. I can help out if you need it. >> >>-brian >> >>On Nov 20, 2012, at 6:42 PM, Roman Garcia wrote: >> >>> +1 >>> We also host our packages (kafka-scala28 and kafka-scala292) on our Nexus >>> server >>> Multiple Scala versions support would be nice as well. >>> >>> >>> On Tue, Nov 20, 2012 at 9:36 PM, Evan Chan <e...@ooyala.com> wrote: >>> >>>> +1. >>>> We hosted our own built version of Kafka on our Nexus server as well. >>>> >>>> -Evan >>>> >>>> >>>> On Tue, Nov 20, 2012 at 3:27 PM, Chris Riccomini <criccom...@linkedin.com >>>>> wrote: >>>> >>>>> Hey Guys, >>>>> >>>>> I was talking with Jay, and he recommended I forward some feedback along. >>>>> >>>>> I have been playing with Kafka 0.8 this week, and am feeling the pain in >>>>> the lack of Maven support for it. Specifically, it'd be nice if this >>>> stuff >>>>> were: >>>>> >>>>> 1. In Apache's SNAPSHOT repository >>>>> 2. In some release repository. >>>>> >>>>> I am pretty sure that you guys are aware that it'd be nice to have, but I >>>>> think I'd like to elevate the priority to blocker, or at least pretty >>>>> critical. >>>>> >>>>> From a community adoption perspective, it's really damaging to the >>>> project >>>>> to not have it easily accessible in a repository. To be blunt, if I >>>> hadn't >>>>> heard of Kafka (and didn't know you guys), and I came across the page, >>>> and >>>>> discovered that it had no maven coordinates, I'd move on to other >>>> solutions >>>>> without a second glance. To me, it looks as bad as having no commits for >>>>> the project in months. It looks unmaintained. >>>>> >>>>> If you look at what's already going on with the community, you'll see a >>>>> lot of pretty rough things being done to try and get around this issue. >>>>> >>>>> 1. Storm has its own publication: >>>> https://clojars.org/storm/storm-kafka >>>>> 2. SenseiDB has it committed in code, and runs a manual install. This >>>>> makes it pretty rough if anyone DEPENDS on SenseiDB, as they, in turn, >>>> must >>>>> do the same thing. >>>>> https://github.com/senseidb/sensei/blob/master/sensei-gateways/pom.xml >>>>> 3. Druid is hosting its own: >>>>> >>>> https://metamx.artifactoryonline.com/metamx/pub-libs-releases-local/kafka/core-kafka/ >>>>> 4. It's been requested for more than a year: >>>>> https://issues.apache.org/jira/browse/KAFKA-133 >>>>> >>>>> This is only going to get worse when 0.8 is released, as it introduces >>>>> even more unmanaged libraries (metrics, zkclient). I assume, currently, >>>>> that releasing 0.8 is not contingent on getting those libraries >>>> published, >>>>> but I think it should be. This is worth doing correctly. I don't think >>>>> it'll be fun, but I really do think it's a big deal. >>>>> >>>>> Any chance we could get this on the road map soon? I think it falls under >>>>> 2013 community adoption. >>>>> >>>>> Thanks! >>>>> Chris >>>>> >>>> >>>> >>>> >>>> -- >>>> -- >>>> *Evan Chan* >>>> Senior Software Engineer | >>>> e...@ooyala.com | (650) 996-4600 >>>> www.ooyala.com | blog <http://www.ooyala.com/blog> | >>>> @ooyala<http://www.twitter.com/ooyala> >>>> >> >>-- >>Brian ONeill >>Lead Architect, Health Market Science (http://healthmarketscience.com) >>mobile:215.588.6024 >>blog: http://weblogs.java.net/blog/boneill42/ >>blog: http://brianoneill.blogspot.com/ >> >> >> >> > >
