Except that it still has the annoying feature of naming the kafka version
after the scala version, which doesn't make sense, e.g.:
~/.ivy2/local/org.apache/kafka_2.8.0/0.8.0-SNAPSHOT/poms ls -l
-rw-r--r-- 1 jbr jbr 3786 May 7 13:43 kafka_2.8.0.pom
-rw-r--r-- 1 jbr jbr 32 May 7 13:44 kafka_2.8.0.pom.md5
-rw-r--r-- 1 jbr jbr 40 May 7 13:44 kafka_2.8.0.pom.sha1
~/.ivy2/local/org.apache/kafka_2.8.0/0.8.0-SNAPSHOT ls -l jars
-rw-r--r-- 1 jbr jbr 2367457 May 6 15:54 kafka_2.8.0.jar
-rw-r--r-- 1 jbr jbr 32 May 7 13:44 kafka_2.8.0.jar.md5
-rw-r--r-- 1 jbr jbr 40 May 7 13:44 kafka_2.8.0.jar.sha1
I think it was mentioned previously (0.7.x had the same issue) there's an
easy way to fix this (but I don't remember at the moment). Perhaps we
could get this fixed before releasing?
I'd think the maven artifacts should be named 'kafka_0.8.0.pom' or
On Tue, May 7, 2013 at 1:48 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
> Thanks for the tip, this is exactly what I need.
> On Tue, May 7, 2013 at 11:58 AM, Gray, Alex <[EMAIL PROTECTED]> wrote:
>> Hi Jason,
>> I don't know if this will help you, but I'm pulling the source code of
>> kafka down to a local machine and calling:
>> ./sbt update
>> /sbt -Dsbt.log.noformat=true publish-local
>> This will publish the generated pom's and jars to your local ~/.ivy2
>> Once you have that, you can publish those same artifacts to your internal
>> repo and modify your project's pom to download the artifacts from your
>> internal repo.
>> That way, everyone in my group is using the same kafka artifacts that I
>> am building.
>> Alex Gray
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>> Sent: Monday, May 06, 2013 10:27 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: maven integration in 0.8
>> There are a lot of release-oriented tickets still about- here's what I'm
>> following pertaining to packaging & getting
>> Scala 2.10-
>> Deps upgrade-
>> CodaMetrics versioning-
>> On Mon, May 06, 2013 at 04:31:50PM -0700, Jason Rosenberg wrote:
>> > Is there a maven repo we can point to, to just depend on the kafka 0.8
>> > core, and have all the dependencies get pulled in as needed?
>> > For some reason, I had thought this would be available as part of the
>> > 0.8 release....
>> > Or do I need to manually create a pom.xml for the core, and host it on
>> > my nexxus instance (as in 0.7.2?).
>> > Thanks,
>> > Jason