The artifacts are published to Maven Central so nothing you should haveto-do except to specify the libraryDependencies

In regards to 2.10.X support I took a really quick look athttps://issues.apache.org/jira/browse/KAFKA-717 (lots to go through in thatticket it seems) will try some of the patch applys tomorrow and see howthey go. I would be in favor of it being part of the 0.8.0 final if it allgets through and looks good and committing it to the 0.8 branch and notonly trunk but lets see first what is involved building 2.10.0, 2.10.1 and2.10.2 and what is going to take to get it working with the patchessubmitted.

I'm wondering whether there is a reason to prefer one version of scala overanother, if we don't have any other particular scala dependency in ourcode. Are the newer versions better/more efficient, some how? We'veessentially been using 2.8.0 so far, which seems to be fine (so I'm notparticularly inclined to change, but I'm just curious).

One thing I notice, in the pom file, there are 2 dependencies listed forzookeeper, one of which has an exclusion clause, the other does not. Iassume this is not intended:<dependency><groupId>org.apache.zookeeper</groupId><artifactId>zookeeper</artifactId><version>3.3.4</version><exclusions><exclusion><groupId>log4j</groupId><artifactId>log4j</artifactId></exclusion><exclusion><groupId>jline</groupId><artifactId>jline</artifactId></exclusion></exclusions></dependency>

> Hey Joe,>> First off, thanks for doing this!>> I'm trying to use the publication with Gradle, and I'm running into> problems. It's giving me a funky exception. I did some digging, and> apparently the exception implies that Gradle has been given a 1.0 pom.>> I took a look at the Kafka pom:>>> https://repository.apache.org/content/groups/public/org/apache/kafka/kafka_> 2.9.2/0.8.0-beta1/kafka_2.9.2-0.8.0-beta1.pom>>> It is indeed interesting. It appears to be a 2.0 pom, but it has a parent> pointing to org.apache (?!). I dug around, and I haven't seen any other> POMs with this style. I am not Maven expert, but at this point, it seems> like the POMs Maven Central are somewhat broken in that regard.>> Have you successfully used the POMs with anything other than SBT? I> noticed you're including "intransitive" in the SBT coordinates. Why is> that? In general, we'd want Kafka's transitive dependencies to be pulled> in, as well. Are you turning off transitivity because of an issue similar> to the one I'm seeing?>> Thanks!> Chris>> On 7/14/13 6:32 PM, "Joe Stein" <[EMAIL PROTECTED]> wrote:>> >With SBT you can use 0.8.1-beta built with any of these four Scala> >versions> >in libraryDependencies now> >> >"org.apache.kafka" % "kafka_2.9.2" % "0.8.0-beta1" intransitive()> >> >or> >> >"org.apache.kafka" % "kafka_2.9.1" % "0.8.0-beta1" intransitive()> >> >or> >> >"org.apache.kafka" % "kafka_2.8.2" % "0.8.0-beta1" intransitive()> >> >or> >> >"org.apache.kafka" % "kafka_2.8.0" % "0.8.0-beta1" intransitive()> >> >> >/*> >Joe Stein> >http://www.linkedin.com/in/charmalloc> >Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>> >*/>>--

> Hey Joe,>> The error I see is:>> 10:35:30.431 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build> failed with an exception.> 10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter]> 10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:> 10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter] Could not resolve> all dependencies for configuration ':samsa-kafka_2.9.2:compile'.> 10:35:30.433 [ERROR] [org.gradle.BuildExceptionReporter] > Could not> resolve org.apache.kafka:kafka_2.9.2:0.8.0-beta1.> 10:35:30.433 [ERROR] [org.gradle.BuildExceptionReporter] Required by:> 10:35:30.433 [ERROR] [org.gradle.BuildExceptionReporter]> samsa:samsa-kafka_2.9.2:0.7.0> 10:35:30.434 [ERROR] [org.gradle.BuildExceptionReporter] > null name> not allowed>> All I could find on the subject was this:>> http://forums.gradle.org/gradle/topics/illegalargumentexception_null_name_n> ot_allowed_resolving_org_iso_relax_verifier_jaxp_validation_isorelax_jaxp_b> ridge_1_0-cavg1>>> As far as I can tell, SBT's "intransitive()" method disabled ALL> transitive dependencies:>> "By default, these declarations fetch all project dependencies,> transitively. In some instances, you may find that the dependencies listed> for a project aren't necessary for it to build. Projects using the Felix> OSGI framework, for instance, only explicitly require its main jar to> compile and run. Avoid fetching artifact dependencies with either> intransitive() or notTransitive(), as in this example:">>> -- https://github.com/harrah/xsbt/wiki/Library-Management>>> I tried doing the Gradle equivalent of SBT's intransitive:>> compile("org.apache.kafka:kafka_$scalaVersion:$kafkaVersion@jar") {> transitive = false> }>> The build still fails with that error.>>> Cheers,>> Chris>> On 7/15/13 10:34 AM, "Joe Stein" <[EMAIL PROTECTED]> wrote:>> >What is/are the error(s) you are getting?> >> >"intransitive" in the SBT line is so that SBT does not fetch the libraries> >what is set for exclusion in the POM> >> >an example of an error if you don't do use what should be excluded is in> >https://issues.apache.org/jira/browse/KAFKA-974> >> >> >On Mon, Jul 15, 2013 at 1:30 PM, Chris Riccomini> ><[EMAIL PROTECTED]>wrote:> >> >> Hey Joe,> >>> >> First off, thanks for doing this!> >>> >> I'm trying to use the publication with Gradle, and I'm running into> >> problems. It's giving me a funky exception. I did some digging, and> >> apparently the exception implies that Gradle has been given a 1.0 pom.> >>> >> I took a look at the Kafka pom:> >>> >>> >>> >>> https://repository.apache.org/content/groups/public/org/apache/kafka/kafk> >>a_> >> 2.9.2/0.8.0-beta1/kafka_2.9.2-0.8.0-beta1.pom> >>> >>> >> It is indeed interesting. It appears to be a 2.0 pom, but it has a> >>parent> >> pointing to org.apache (?!). I dug around, and I haven't seen any other> >> POMs with this style. I am not Maven expert, but at this point, it seems> >> like the POMs Maven Central are somewhat broken in that regard.> >>> >> Have you successfully used the POMs with anything other than SBT? I> >> noticed you're including "intransitive" in the SBT coordinates. Why is> >> that? In general, we'd want Kafka's transitive dependencies to be pulled> >> in, as well. Are you turning off transitivity because of an issue> >>similar> >> to the one I'm seeing?> >>> >> Thanks!> >> Chris> >>> >> On 7/14/13 6:32 PM, "Joe Stein" <[EMAIL PROTECTED]> wrote:> >>> >> >With SBT you can use 0.8.1-beta built with any of these four Scala> >> >versions> >> >in libraryDependencies now> >> >> >> >"org.apache.kafka" % "kafka_2.9.2" % "0.8.0-beta1" intransitive()

> Hey Joe,>> The error I see is:>> 10:35:30.431 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build> failed with an exception.> 10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter]> 10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:> 10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter] Could not resolve> all dependencies for configuration ':samsa-kafka_2.9.2:compile'.> 10:35:30.433 [ERROR] [org.gradle.BuildExceptionReporter] > Could not> resolve org.apache.kafka:kafka_2.9.2:0.8.0-beta1.> 10:35:30.433 [ERROR] [org.gradle.BuildExceptionReporter] Required by:> 10:35:30.433 [ERROR] [org.gradle.BuildExceptionReporter]> samsa:samsa-kafka_2.9.2:0.7.0> 10:35:30.434 [ERROR] [org.gradle.BuildExceptionReporter] > null name> not allowed>> All I could find on the subject was this:>> http://forums.gradle.org/gradle/topics/illegalargumentexception_null_name_n> ot_allowed_resolving_org_iso_relax_verifier_jaxp_validation_isorelax_jaxp_b> ridge_1_0-cavg1>>> As far as I can tell, SBT's "intransitive()" method disabled ALL> transitive dependencies:>> "By default, these declarations fetch all project dependencies,> transitively. In some instances, you may find that the dependencies listed> for a project aren't necessary for it to build. Projects using the Felix> OSGI framework, for instance, only explicitly require its main jar to> compile and run. Avoid fetching artifact dependencies with either> intransitive() or notTransitive(), as in this example:">>> -- https://github.com/harrah/xsbt/wiki/Library-Management>>> I tried doing the Gradle equivalent of SBT's intransitive:>> compile("org.apache.kafka:kafka_$scalaVersion:$kafkaVersion@jar") {> transitive = false> }>> The build still fails with that error.>>> Cheers,>> Chris>> On 7/15/13 10:34 AM, "Joe Stein" <[EMAIL PROTECTED]> wrote:>> >What is/are the error(s) you are getting?> >> >"intransitive" in the SBT line is so that SBT does not fetch the libraries> >what is set for exclusion in the POM> >> >an example of an error if you don't do use what should be excluded is in> >https://issues.apache.org/jira/browse/KAFKA-974> >> >> >On Mon, Jul 15, 2013 at 1:30 PM, Chris Riccomini> ><[EMAIL PROTECTED]>wrote:> >> >> Hey Joe,> >>> >> First off, thanks for doing this!> >>> >> I'm trying to use the publication with Gradle, and I'm running into> >> problems. It's giving me a funky exception. I did some digging, and> >> apparently the exception implies that Gradle has been given a 1.0 pom.> >>> >> I took a look at the Kafka pom:> >>> >>> >>> >>> https://repository.apache.org/content/groups/public/org/apache/kafka/kafk> >>a_> >> 2.9.2/0.8.0-beta1/kafka_2.9.2-0.8.0-beta1.pom> >>> >>> >> It is indeed interesting. It appears to be a 2.0 pom, but it has a> >>parent> >> pointing to org.apache (?!). I dug around, and I haven't seen any other

I think the issue is that I had to-do multiple pushes to nexus to get thisto work (unfortunately) and perhaps maven central did not overwrite like itdid with apache rather appending and meshing the poms together. The POM inmaven central looks like a combination of what I was doing inhttps://issues.apache.org/jira/browse/KAFKA-974

Please create a JIRA however I suspect when we do another release (either0.8.0-beta2 or 0.8.0) this will be correct and 1:1 from apache repo becauseI won't be doing multiple pushes like i had to-do here