Maven repo for kafka?

[Jason Rosenberg <jb...@squareup.com>]

Hello,

I'm just getting started ramping up with kafka (pretty cool so far).

I wasn't able to find a public repo for the kafka jars (and in looking back
at the archives for this list, it seems that this question comes up from
time to time).

Are there any plans to make kafka integrate better with maven, via a public
repo?

I was able to generate a pom.xml, using "./sbt make-pom".  And then upload
the pom and the jar to our nexus repo, etc.  So that's a stop-gap solution
(albeit cumbersome).

I am curious, why does the generated pom have a groupId of "kafka" and an
artifactId of "kafka-core_2.8.0".  (what's the 2.8.0 for?).

Traditionally, apache projects have maven group ids like "org.apache.kafka"
and artifactId like "kafka-core".

Thoughts?

Jason

Re: Maven repo for kafka?

[Neha Narkhede <ne...@gmail.com>]

Jason,

This has been on our plate for quite some time now. SBT 0.7.5, by
default, attaches the "_2.8.0" at the end of the artifact name
and for some odd reason we have set the groupid to "kafka" (see
KafkaProject.scala)

    override def artifactID = "kafka"

I suspect this is something that probably made sense in a much older
Kafka version, but hasn't evolved gracefully after our move to Apache.
But, we are open to accepting patches if you've found the ./sbt
make-pom to work with the above mentioned change.

Thanks,
Neha

On Wed, Oct 17, 2012 at 2:23 AM, Michal Haris
<mi...@visualdna.com> wrote:
> Hi, I have an svn repo which only contains an extrnal to the kafka svn
> core/src and a pom.xml which is a modification of the one I found on kafka
> jira.
> svn co http://xp-dev.com/svn/gridport.co/artifacts/kafka-core/
> cd kafka-core
> mvn scala:compile
>
> You can then modify the  <distributionManagement/> of the contained pom.xml
> to deploy to your own maven and then use as a dependency for producers' and
> consumers' api:
> mvn deploy
>
> Or build a standalone jar for packaging kafka server itself:
> mvn assembly:single
>
> Michal,
>
>
> On 9 October 2012 19:40, Jason Rosenberg <jb...@squareup.com> wrote:
>
>> Hello,
>>
>> I'm just getting started ramping up with kafka (pretty cool so far).
>>
>> I wasn't able to find a public repo for the kafka jars (and in looking back
>> at the archives for this list, it seems that this question comes up from
>> time to time).
>>
>> Are there any plans to make kafka integrate better with maven, via a public
>> repo?
>>
>> I was able to generate a pom.xml, using "./sbt make-pom".  And then upload
>> the pom and the jar to our nexus repo, etc.  So that's a stop-gap solution
>> (albeit cumbersome).
>>
>> I am curious, why does the generated pom have a groupId of "kafka" and an
>> artifactId of "kafka-core_2.8.0".  (what's the 2.8.0 for?).
>>
>> Traditionally, apache projects have maven group ids like "org.apache.kafka"
>> and artifactId like "kafka-core".
>>
>> Thoughts?
>>
>> Jason
>>
>
>
>
> --
> Michal Haris
> Software Engineer
>
> VisualDNA | 7 Moor Street, London, W1D 5NB
> www.visualdna.com | t: +44 (0) 207 734 7033

Re: Maven repo for kafka?

[Michal Haris <mi...@visualdna.com>]

Hi, I have an svn repo which only contains an extrnal to the kafka svn
core/src and a pom.xml which is a modification of the one I found on kafka
jira.
svn co http://xp-dev.com/svn/gridport.co/artifacts/kafka-core/
cd kafka-core
mvn scala:compile

You can then modify the  <distributionManagement/> of the contained pom.xml
to deploy to your own maven and then use as a dependency for producers' and
consumers' api:
mvn deploy

Or build a standalone jar for packaging kafka server itself:
mvn assembly:single

Michal,


On 9 October 2012 19:40, Jason Rosenberg <jb...@squareup.com> wrote:

> Hello,
>
> I'm just getting started ramping up with kafka (pretty cool so far).
>
> I wasn't able to find a public repo for the kafka jars (and in looking back
> at the archives for this list, it seems that this question comes up from
> time to time).
>
> Are there any plans to make kafka integrate better with maven, via a public
> repo?
>
> I was able to generate a pom.xml, using "./sbt make-pom".  And then upload
> the pom and the jar to our nexus repo, etc.  So that's a stop-gap solution
> (albeit cumbersome).
>
> I am curious, why does the generated pom have a groupId of "kafka" and an
> artifactId of "kafka-core_2.8.0".  (what's the 2.8.0 for?).
>
> Traditionally, apache projects have maven group ids like "org.apache.kafka"
> and artifactId like "kafka-core".
>
> Thoughts?
>
> Jason
>



-- 
Michal Haris
Software Engineer

VisualDNA | 7 Moor Street, London, W1D 5NB
www.visualdna.com | t: +44 (0) 207 734 7033