From users-return-4291-apmail-kafka-users-archive=kafka.apache.org@kafka.apache.org Tue May 7 22:52:04 2013 Return-Path: X-Original-To: apmail-kafka-users-archive@www.apache.org Delivered-To: apmail-kafka-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8F0DF59A for ; Tue, 7 May 2013 22:52:04 +0000 (UTC) Received: (qmail 52482 invoked by uid 500); 7 May 2013 22:52:04 -0000 Delivered-To: apmail-kafka-users-archive@kafka.apache.org Received: (qmail 52462 invoked by uid 500); 7 May 2013 22:52:04 -0000 Mailing-List: contact users-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@kafka.apache.org Delivered-To: mailing list users@kafka.apache.org Received: (qmail 52451 invoked by uid 99); 7 May 2013 22:52:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 22:52:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jbr@squareup.com designates 209.85.223.170 as permitted sender) Received: from [209.85.223.170] (HELO mail-ie0-f170.google.com) (209.85.223.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 22:52:00 +0000 Received: by mail-ie0-f170.google.com with SMTP id aq17so2073001iec.15 for ; Tue, 07 May 2013 15:51:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=squareup.com; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=UGuEdvWJKvaxgebDqE0VbpdEMIsdVYB3E0TApfYIIvM=; b=SUczJyKZcsXPxyeN7DqedjjLc5cJKdq1wJZrxXv4/ZVn+661KmVpf47VkhQYCYmEtT R8jHpGRtIzj9BzOBl/bhaXTl//LAXuZHblUd3hTHiMNw9YGDRMEELIRwTwMu71CRbCbe 092oSuwtm60bLMatcnYCQj0uK+nJ1wzCvEyWg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=UGuEdvWJKvaxgebDqE0VbpdEMIsdVYB3E0TApfYIIvM=; b=mWMPCQC+hDnV+MwSq6SSndGrFJ2Wwn7n2cGCSJ6o+XIx++WlGCnHK5D0yTYdtTf1nO yD3cG1E6b97xG7L8AaH0Z9OIGE094AAgysap0aGPyFJjwpMmyXw3iSBtj3VwE8ZsYiGM 2b9ae2Cx3eq8gRKTPFWe4Ixya7wYhE2xtzpQICUB494x16mx5pfqoT9hjCYDcHv9HkUl TEzi+/nIcwbQ/Wh+VU2A+aLvhJz2NPiOOrDtZ/1ziSz9oHp6V3yyOjyfN/K7Euj/dCLE 7CUNpSU5+eODFtp4W7qagNnCLm80bVQdQuJGbxfBBetctdpoqvrSpUkFFVIXQECdokDV 45JQ== MIME-Version: 1.0 X-Received: by 10.50.237.71 with SMTP id va7mr4896256igc.88.1367967099665; Tue, 07 May 2013 15:51:39 -0700 (PDT) Received: by 10.50.180.196 with HTTP; Tue, 7 May 2013 15:51:39 -0700 (PDT) In-Reply-To: References: <20130507022720.GB31169@voodoowarez.com> <3EA0FFD0A48C5946A7B95C4A6AE2438C4806F9@MAILDB2.i3domain.inin.com> Date: Tue, 7 May 2013 15:51:39 -0700 Message-ID: Subject: Re: maven integration in 0.8 From: Jason Rosenberg To: users@kafka.apache.org Content-Type: multipart/alternative; boundary=f46d0447a2430a545404dc28a9a4 X-Gm-Message-State: ALoCoQmozn0D8rnCh7nqIOFuv1xZM8a3d5p+fTCnlz/eRNtdlchi/a83qyv5BX+56DItp7zSFjld X-Virus-Checked: Checked by ClamAV on apache.org --f46d0447a2430a545404dc28a9a4 Content-Type: text/plain; charset=ISO-8859-1 Perhaps, but you don't want to version your kafka artifacts as just 2.8.0. The way you handle something like that with maven, is to include the dependency on scala 2.8.0 in the the kafka pom's dependency list. e.g.: org.scala-lang scala-library 2.8.0 But the version of kafka is 0.8.0, not 2.8.0. Otherwise, how is one to distinguish it from a kafka 0.7.2 jar? What I've done now, is to actually include the 2.8.0 in the artifactId, but not the version id, so: org.apache kafka_2.8.0 jar kafka 0.8.0-SHA kafka So, in the maven repo it looks like: /org/apache/kafka_2.8.0/kafka_2.8.0-0.8.0-SHA.jar Make sense? I'm contemplating removing the '_2.8.0' bit though, since I don't think it makes sense there, more I think about it. I replace the 'SHA' part with the actual git sha of the current build (once we have a release, I can remove the SHA part). Jason On Tue, May 7, 2013 at 3:00 PM, Alex Zuzin wrote: > It's actually a rather helpful convention SBT has instituted to deal with > bytecode incompatibilities between the different versions of Scala. I > wouldn't advise removing it at all - using a 2.8.0-built project in > production with Scala 2.9 or higher is courting disaster. > > -- > Alex Zuzin > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > On Tuesday, May 7, 2013 at 14:26, Jason Rosenberg wrote: > > > 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 > > total 24 > > -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 > > > > and > > > > ~/.ivy2/local/org.apache/kafka_2.8.0/0.8.0-SNAPSHOT ls -l jars > > total 4640 > > -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 > > 'kakfa_0.8.0-SNAPSHOT.pom', etc... > > > > Jason > > > > > > > > > > On Tue, May 7, 2013 at 1:48 PM, Jason Rosenberg > wrote: > > > > > Alex, > > > > > > Thanks for the tip, this is exactly what I need. > > > > > > Jason > > > > > > > > > On Tue, May 7, 2013 at 11:58 AM, Gray, Alex > 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 > > > > directory. > > > > > > > > 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: rektide@voodoowarez.com [mailto:rektide@voodoowarez.com] > > > > Sent: Monday, May 06, 2013 10:27 PM > > > > To: users@kafka.apache.org > > > > 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 > > > > shipped- > > > > > > > > Maven- > > > > > > > > > https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > > > Scala 2.10- > > > > > > > > > https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > > > Deps upgrade- > > > > > > > > > https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > > > CodaMetrics versioning- > > > > > > > > > https://issues.apache.org/jira/browse/KAFKA-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > > > > > > > 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 > > --f46d0447a2430a545404dc28a9a4--