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

+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 <[EMAIL PROTECTED]>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 |
[EMAIL PROTECTED] | (650) 996-4600
www.ooyala.com | blog <http://www.ooyala.com/blog> |
@ooyala<http://www.twitter.com/ooyala>

+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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]
> >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 |
> [EMAIL PROTECTED] | (650) 996-4600
> www.ooyala.com | blog <http://www.ooyala.com/blog> |
> @ooyala<http://www.twitter.com/ooyala>
>

++ to both Maven packages and multiple Scala versions.

As above, we host our own 2.9.2 build in Nexus. Seems crazy everyone is
doing the same thing and constantly repeating work.
On Tue, Nov 20, 2012 at 5:42 PM, Roman Garcia <[EMAIL PROTECTED]>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 <[EMAIL PROTECTED]> 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 <
> [EMAIL PROTECTED]
> > >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 |
> > [EMAIL PROTECTED] | (650) 996-4600
> > www.ooyala.com | blog <http://www.ooyala.com/blog> |
> > @ooyala<http://www.twitter.com/ooyala>
> >
>

--
Matthew Rathbone
Foursquare | Software Engineer | Server Engineering Team
[EMAIL PROTECTED] | @rathboma <http://twitter.com/rathboma> |
4sq<http://foursquare.com/rathboma>

+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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]
>>> 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 |
>> [EMAIL PROTECTED] | (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/

+1

We have kafka + deps defined in a custom Ivy repo

On Nov 20, 2012, at 7:18 PM, Matthew Rathbone wrote:

> ++ to both Maven packages and multiple Scala versions.
>
> As above, we host our own 2.9.2 build in Nexus. Seems crazy everyone is
> doing the same thing and constantly repeating work.
>
>
> On Tue, Nov 20, 2012 at 5:42 PM, Roman Garcia <[EMAIL PROTECTED]>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 <[EMAIL PROTECTED]> 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 <
>> [EMAIL PROTECTED]
>>>> 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 |
>>> [EMAIL PROTECTED] | (650) 996-4600
>>> www.ooyala.com | blog <http://www.ooyala.com/blog> |
>>> @ooyala<http://www.twitter.com/ooyala>
>>>
>>
>
>
>
> --
> Matthew Rathbone
> Foursquare | Software Engineer | Server Engineering Team
> [EMAIL PROTECTED] | @rathboma <http://twitter.com/rathboma> |
> 4sq<http://foursquare.com/rathboma>

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 <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]
>>>> 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 |
>>> [EMAIL PROTECTED] | (650) 996-4600
>>> www.ooyala.com | blog <http://www.ooyala.com/blog> |

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 <[EMAIL PROTECTED]>
>To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>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 <[EMAIL PROTECTED]>
>>To: [EMAIL PROTECTED]
>>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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]
>>>>> 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,

+100....
I've been manually creating poms and uploading jars to our nexus repo too,
not ideal at all....

On Tue, Nov 20, 2012 at 6:48 PM, Otis Gospodnetic <
[EMAIL PROTECTED]> wrote:

> 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 <[EMAIL PROTECTED]>
> >To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> >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 <[EMAIL PROTECTED]>
> >>To: [EMAIL PROTECTED]
> >>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 <[EMAIL PROTECTED]> 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 <
> [EMAIL PROTECTED]
> >>>>> 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

For what it's worth, I also publish releases on clojars.org

On Wed, Nov 21, 2012 at 7:23 AM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
> +100....
> I've been manually creating poms and uploading jars to our nexus repo too,
> not ideal at all....
>
> On Tue, Nov 20, 2012 at 6:48 PM, Otis Gospodnetic <
> [EMAIL PROTECTED]> wrote:
>
>> 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 <[EMAIL PROTECTED]>
>> >To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> >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 <[EMAIL PROTECTED]>
>> >>To: [EMAIL PROTECTED]
>> >>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 <[EMAIL PROTECTED]> 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 <
>> [EMAIL PROTECTED]
>> >>>>> 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

Hmmm......none of the ones there seem like the canonical version, how do I
know which of the ones published there is the one to use?

(I searched for 'kafka' on there...).

Jason

On Tue, Nov 20, 2012 at 10:29 PM, Pierre-Yves Ritschard <[EMAIL PROTECTED]>wrote:

> For what it's worth, I also publish releases on clojars.org
>
> On Wed, Nov 21, 2012 at 7:23 AM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
> > +100....
> > I've been manually creating poms and uploading jars to our nexus repo
> too,
> > not ideal at all....
> >
> > On Tue, Nov 20, 2012 at 6:48 PM, Otis Gospodnetic <
> > [EMAIL PROTECTED]> wrote:
> >
> >> 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 <[EMAIL PROTECTED]>
> >> >To: "[EMAIL PROTECTED]" <
> [EMAIL PROTECTED]>
> >> >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 <[EMAIL PROTECTED]>
> >> >>To: [EMAIL PROTECTED]
> >> >>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 <[EMAIL PROTECTED]> 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 <
> >> [EMAIL PROTECTED]
> >> >>>>> 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,
>

Thanks for the feedback everyone.

I do want to mention that the lack of action on this is not because we
don't care. Most all the committers have been almost entirely heads down on
getting replication, the network re-architecture, the log reimplementation,
and the system test framework done for 0.8 for the last 9 months or so.
That represents a pretty huge chunk of code (from around 13k loc to almost
19k loc). There just hasn't been a lot of slack time to spend on other
important things like the build system, website, documentation, etc. The
good news is that we are feature complete on 0.8 and though there is a lot
of hardening left to do, it does appear to work as we hoped, which is
incredibly exciting to me personally.

A second practical problem seems to be that almost none of the committers
seems to know either SBT or maven well enough to just sit down and do this.
So thanks a lot to people who have been trying to help us out.

-Jay
On Tue, Nov 20, 2012 at 3:27 PM, Chris Riccomini <[EMAIL PROTECTED]>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
>

I'm sure there are a number of us with working SBT scripts that publish to
Sonatype / Maven central (I have one for another OSS project), that we can
share.

There are a few steps independent of SBT, however, including registering on
Sonatype, and getting a GPG key.

Here is one useful guide:
http://www.scala-sbt.org/release/docs/Community/Using-Sonatype.html

-Evan
On Wed, Nov 21, 2012 at 8:52 AM, Jay Kreps <[EMAIL PROTECTED]> wrote:

> Thanks for the feedback everyone.
>
> I do want to mention that the lack of action on this is not because we
> don't care. Most all the committers have been almost entirely heads down on
> getting replication, the network re-architecture, the log reimplementation,
> and the system test framework done for 0.8 for the last 9 months or so.
> That represents a pretty huge chunk of code (from around 13k loc to almost
> 19k loc). There just hasn't been a lot of slack time to spend on other
> important things like the build system, website, documentation, etc. The
> good news is that we are feature complete on 0.8 and though there is a lot
> of hardening left to do, it does appear to work as we hoped, which is
> incredibly exciting to me personally.
>
> A second practical problem seems to be that almost none of the committers
> seems to know either SBT or maven well enough to just sit down and do this.
> So thanks a lot to people who have been trying to help us out.
>
> -Jay
>
>
> On Tue, Nov 20, 2012 at 3:27 PM, Chris Riccomini <[EMAIL PROTECTED]
> >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 |
[EMAIL PROTECTED] | (650) 996-4600
www.ooyala.com | blog <http://www.ooyala.com/blog> |
@ooyala<http://www.twitter.com/ooyala>

You may want to read this as well:

http://www.apache.org/dev/publishing-maven-artifacts.html
Regards,
Alan

On Nov 21, 2012, at 10:01 AM, Evan Chan wrote:

> I'm sure there are a number of us with working SBT scripts that publish to
> Sonatype / Maven central (I have one for another OSS project), that we can
> share.
>
> There are a few steps independent of SBT, however, including registering on
> Sonatype, and getting a GPG key.
>
> Here is one useful guide:
> http://www.scala-sbt.org/release/docs/Community/Using-Sonatype.html
>
> -Evan
>
>
> On Wed, Nov 21, 2012 at 8:52 AM, Jay Kreps <[EMAIL PROTECTED]> wrote:
>
>> Thanks for the feedback everyone.
>>
>> I do want to mention that the lack of action on this is not because we
>> don't care. Most all the committers have been almost entirely heads down on
>> getting replication, the network re-architecture, the log reimplementation,
>> and the system test framework done for 0.8 for the last 9 months or so.
>> That represents a pretty huge chunk of code (from around 13k loc to almost
>> 19k loc). There just hasn't been a lot of slack time to spend on other
>> important things like the build system, website, documentation, etc. The
>> good news is that we are feature complete on 0.8 and though there is a lot
>> of hardening left to do, it does appear to work as we hoped, which is
>> incredibly exciting to me personally.
>>
>> A second practical problem seems to be that almost none of the committers
>> seems to know either SBT or maven well enough to just sit down and do this.
>> So thanks a lot to people who have been trying to help us out.
>>
>> -Jay
>>
>>
>> On Tue, Nov 20, 2012 at 3:27 PM, Chris Riccomini <[EMAIL PROTECTED]
>>> 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*

Chris,

Thanks for letting us know. We will be looking into this.

Thanks,

Jun

On Tue, Nov 20, 2012 at 3:27 PM, Chris Riccomini <[EMAIL PROTECTED]>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
>