You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2011/09/15 17:50:09 UTC
[jira] [Created] (KAFKA-133) Publish kafka jar to a public maven
repository
Publish kafka jar to a public maven repository
----------------------------------------------
Key: KAFKA-133
URL: https://issues.apache.org/jira/browse/KAFKA-133
Project: Kafka
Issue Type: Improvement
Reporter: Neha Narkhede
The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (KAFKA-133) Publish kafka jar to a public
maven repository
Posted by will martin <wm...@gmail.com>.
Folks: If sonatype trails apache||| maven supports pulling code and
compiling (just like sbt) from github and other repositories. So why don't
we just script the maven and try it out. I just spent a year with
Streamsage (now Comcast) building under the most mature process across
Comcast (which was noticed during due-diligence) and it was all agile:
atlassian and archiva/artifactory/sonatype/svn/nagios/opennms/hdfs/azkhaban
... You can assign it to me if you want; if I can have 7 calendar days to
make sure it is robust, stable, and extensible. Still it might make more
sense for a commiter to handle the few component builds necessary.
??
Bill
While you may
On Mon, Oct 8, 2012 at 2:36 PM, Chris Aniszczyk (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471741#comment-13471741]
>
> Chris Aniszczyk commented on KAFKA-133:
> ---------------------------------------
>
> bump... +1
>
> Can this be done? We're looking to consume Kafka...
>
> At least to the Sonatype OSS repo or somewhere?
>
> https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
>
> > Publish kafka jar to a public maven repository
> > ----------------------------------------------
> >
> > Key: KAFKA-133
> > URL: https://issues.apache.org/jira/browse/KAFKA-133
> > Project: Kafka
> > Issue Type: Improvement
> > Affects Versions: 0.6
> > Reporter: Neha Narkhede
> > Labels: patch
> > Attachments: pom.xml
> >
> >
> > The released kafka jar must be download manually and then deploy to a
> private repository before they can be used by a developer using maven2.
> > Similar to other Apache projects, it will be nice to have a way to
> publish Kafka releases to a public maven repo.
> > In the past, we gave it a try using sbt publish to Sonatype Nexus maven
> repo, but ran into some authentication problems. It will be good to revisit
> this and get it resolved.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506839#comment-13506839 ]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
That's great. Thanks a lot Otis for seeing this through. We will look into the process of publishing to Maven now.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6, 0.8
> Reporter: Neha Narkhede
> Labels: patch
> Fix For: 0.8
>
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Pierre-Yves Ritschard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109011#comment-13109011 ]
Pierre-Yves Ritschard commented on KAFKA-133:
---------------------------------------------
I think it would also be nice to publish the resulting clojure client jar to a maven repo, so client clojure code could benefit easily.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Reporter: Neha Narkhede
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Thomas Dudziak (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Dudziak updated KAFKA-133:
---------------------------------
Attachment: pom.xml
Fwiw, this is the pom I currently use for uploading to our internal maven repo.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Patricio Echague (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177768#comment-13177768 ]
Patricio Echague commented on KAFKA-133:
----------------------------------------
Hi, has there been any progress on this ticket ?
a pom file in place will be very useful to set up a project.
Thanks for the effort here.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504367#comment-13504367 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
Update on the zklient front - it's getting Sonatyped: https://issues.sonatype.org/browse/OSSRH-4783 and Johannes Zillmann says it should be in there in 2-3 days.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6, 0.8
> Reporter: Neha Narkhede
> Labels: patch
> Fix For: 0.8
>
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Joshua Hartman (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Hartman updated KAFKA-133:
---------------------------------
Labels: patch (was: )
Affects Version/s: 0.6
Status: Patch Available (was: Open)
commit e6f067d538d4902f64f8397256fe8d967e036bc6
Author: Joshua Hartman <jh...@linkedin.com>
Date: Mon Oct 24 10:56:12 2011 -0700
Initial attempt at sbt upgrade.
diff --git a/lib/sbt-launch.jar b/lib/sbt-launch.jar
deleted file mode 100644
index 67ee369..0000000
Binary files a/lib/sbt-launch.jar and /dev/null differ
diff --git a/project/Build.scala b/project/Build.scala
new file mode 100644
index 0000000..085809b
--- /dev/null
+++ b/project/Build.scala
@@ -0,0 +1,147 @@
+import sbt._
+import Keys._
+import xml.NodeSeq
+
+object BuildSettings {
+ val exclusions = Seq("javax", "jmxri", "jmxtools", "mail", "jms")
+ val ivyExclude = <dependencies>{exclusions.map ( e => <exclude module={e}/>)}</dependencies>
+
+ val buildSettings = Defaults.defaultSettings ++ Seq (
+ organization := "kafka",
+ version := "0.7",
+ crossScalaVersions := Seq("2.8.1", "2.9.1"),
+ ivyXML := ivyExclude
+ )
+
+ def buildPomExtra(pom: NodeSeq, name: String, desc: String) = {
+ pom ++ Seq(
+ <name>
+ {name}
+ </name>,
+ <description>
+ {desc}
+ </description>,
+ <url>http://incubator.apache.org/kafka</url>,
+ <licenses>
+ <license>
+ <name>Apache</name>
+ <url>http://svn.apache.org/repos/asf/incubator/kafka/trunk/LICENSE</url>
+ <distribution>repo</distribution>
+ </license>
+ </licenses>,
+ <scm>
+ <url>http://svn.apache.org/repos/asf/incubator/kafka/trunk/</url>
+ <connection>scm:svn:http://svn.apache.org/repos/asf/incubator/kafka/trunk</connection>
+ <developerConnection>scm:svn:https://foo.googlecode.com/svn/trunk/</developerConnection>
+ <connection>scm:git:git://github.com/linkedin-sna/norbert.git</connection>
+ </scm>,
+ <developers>
+ <developer>
+ <id>jkreps</id>
+ <name>Jay Kreps</name>
+ <url>http://www.linkedin.com/in/jaykreps</url>
+ </developer>
+ <developer>
+ <id>junrao</id>
+ <name>Jun Rao</name>
+ <url>http://www.linkedin.com/in/junrao</url>
+ </developer>
+ <developer>
+ <id>nehanarkhede</id>
+ <name>Joshua Hartman</name>
+ <url>http://www.linkedin.com/in/nehanarkhede</url>
+ </developer>
+ </developers>
+ )
+ }
+}
+
+object Resolvers {
+ val oracleRepo = "Oracle Maven 2 Repository" at "http://download.oracle.com/maven"
+ val jBossRepo = "JBoss Maven 2 Repository" at "http://repository.jboss.com/maven2"
+ val kafkaResolvers = Seq(oracleRepo, jBossRepo)
+}
+
+object CoreDependencies {
+// TODO jhartman: When sbt 0.11.1 is ready, we can use the following code instead of ivy xml
+// val exclusions = Seq("javax", "jmxri", "jmxtools", "mail", "jms") map (n => ExclusionRule(name = n))
+// val log4j = ("log4j" % "log4j" % "1.2.15") excludeAll (exclusions :_*)
+
+ val log4j = ("log4j" % "log4j" % "1.2.15")
+ val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
+ val deps = Seq(log4j, jopt)
+}
+
+object HadoopProducerDependencies {
+ val avro = "org.apache.avro" % "avro" % "1.4.1"
+ val jacksonCore = "org.codehaus.jackson" % "jackson-core-asl" % "1.5.5"
+ val jacksonMapper = "org.codehaus.jackson" % "jackson-mapper-asl" % "1.5.5"
+ val deps = Seq(avro, jacksonCore, jacksonMapper)
+}
+
+object HadoopConsumerDependencies {
+ val jodaTime = "joda-time" % "joda-time" % "1.6"
+ val httpclient = "commons-httpclient" % "commons-httpclient" % "3.1"
+ val deps = Seq(jodaTime, httpclient)
+}
+
+object TestDependencies {
+ val easymock = "org.easymock" % "easymock" % "3.0" % "test"
+ val junit = "junit" % "junit" % "4.1" % "test"
+ val scalaTest = "org.scalatest" % "scalatest" % "1.2" % "test"
+ val deps = Seq(easymock, junit, scalaTest)
+}
+
+object KafkaBuild extends Build {
+ import BuildSettings._
+
+ lazy val core = Project("core", file("core"),
+ settings = buildSettings ++ Seq(
+ libraryDependencies ++= CoreDependencies.deps ++ TestDependencies.deps,
+ resolvers := Resolvers.kafkaResolvers
+ )
+ )
+
+ lazy val examples = Project("examples", file("examples"),
+ settings = buildSettings
+ ) dependsOn (core)
+
+
+ lazy val perf = Project("perf", file("perf"),
+ settings = buildSettings
+ ) dependsOn (core)
+
+ lazy val hadoopProducer = Project("hadoop-producer", file("hadoop-producer"),
+ settings = buildSettings ++ Seq(
+ libraryDependencies ++= HadoopProducerDependencies.deps
+ )
+ ) dependsOn (core)
+
+ lazy val hadoopConsumer = Project("hadoop-consumer", file("hadoop-consumer"),
+ settings = buildSettings ++ Seq(
+ libraryDependencies ++= HadoopConsumerDependencies.deps
+ )
+ ) dependsOn (core)
+
+ lazy val contrib = Project("contrib", file("contrib"), settings = buildSettings) aggregate(hadoopConsumer, hadoopProducer)
+
+ lazy val root = Project("root", file("."),
+ settings = buildSettings ++ Seq(
+ pomExtra <<= (pomExtra, name, description) { buildPomExtra }
+ )) aggregate(core, examples, perf, contrib)
+
+ lazy val full = Project(
+ id = "kafka",
+ base = file("full"),
+ settings = buildSettings ++ Seq(
+ description := "Includes all of kafka project in one",
+ libraryDependencies ++= CoreDependencies.deps ++ TestDependencies.deps ++ HadoopProducerDependencies.deps ++ HadoopConsumerDependencies.deps,
+
+ (unmanagedJars in Compile) <<= (projects.map(unmanagedJars in Compile in _).join).map(_.flatten),
+ (unmanagedSourceDirectories in Compile) <<= projects.map(unmanagedSourceDirectories in Compile in _).join.apply(_.flatten),
+ (managedSourceDirectories in Compile) <<= projects.map(managedSourceDirectories in Compile in _).join.apply(_.flatten),
+
+ pomExtra <<= (pomExtra, name, description) { buildPomExtra }
+ )
+ )
+}
diff --git a/project/build.properties b/project/build.properties
deleted file mode 100644
index 7c14cce..0000000
--- a/project/build.properties
+++ /dev/null
@@ -1,10 +0,0 @@
-#Project properties
-#Mon Feb 28 11:55:49 PST 2011
-project.name=Kafka
-sbt.version=0.7.5
-project.version=0.7
-build.scala.versions=2.8.0
-contrib.root.dir=contrib
-lib.dir=lib
-target.dir=target/scala_2.8.0
-dist.dir=dist
diff --git a/project/build/KafkaProject.scala b/project/build/KafkaProject.scala
index ba682d5..77aafba 100644
--- a/project/build/KafkaProject.scala
+++ b/project/build/KafkaProject.scala
@@ -1,190 +1,190 @@
-import sbt._
-
-class KafkaProject(info: ProjectInfo) extends ParentProject(info) with IdeaProject {
- lazy val core = project("core", "core-kafka", new CoreKafkaProject(_))
- lazy val examples = project("examples", "java-examples", new KafkaExamplesProject(_), core)
- lazy val perf = project("perf", "perf", new KafkaPerfProject(_), core)
- lazy val contrib = project("contrib", "contrib", new ContribProject(_))
-
- lazy val releaseZipTask = core.packageDistTask
-
- val releaseZipDescription = "Compiles every sub project, runs unit tests, creates a deployable release zip file with dependencies, config, and scripts."
- lazy val releaseZip = releaseZipTask dependsOn(core.corePackageAction, core.test, examples.examplesPackageAction, perf.perfPackageAction,
- contrib.producerPackageAction, contrib.consumerPackageAction) describedAs releaseZipDescription
-
- class CoreKafkaProject(info: ProjectInfo) extends DefaultProject(info)
- with IdeaProject with CoreDependencies with TestDependencies {
- val corePackageAction = packageAllAction
-
- //The issue is going from log4j 1.2.14 to 1.2.15, the developers added some features which required
- // some dependencies on various sun and javax packages.
- override def ivyXML =
- <dependencies>
- <exclude module="javax"/>
- <exclude module="jmxri"/>
- <exclude module="jmxtools"/>
- <exclude module="mail"/>
- <exclude module="jms"/>
- </dependencies>
-
- override def repositories = Set(ScalaToolsSnapshots, "JBoss Maven 2 Repository" at "http://repository.jboss.com/maven2",
- "Oracle Maven 2 Repository" at "http://download.oracle.com/maven", "maven.org" at "http://repo2.maven.org/maven2/")
-
- override def artifactID = "kafka"
- override def filterScalaJars = false
-
- // build the executable jar's classpath.
- // (why is it necessary to explicitly remove the target/{classes,resources} paths? hm.)
- def dependentJars = {
- val jars =
- publicClasspath +++ mainDependencies.scalaJars --- mainCompilePath --- mainResourcesOutputPath
- if (jars.get.find { jar => jar.name.startsWith("scala-library-") }.isDefined) {
- // workaround bug in sbt: if the compiler is explicitly included, don't include 2 versions
- // of the library.
- jars --- jars.filter { jar =>
- jar.absolutePath.contains("/boot/") && jar.name == "scala-library.jar"
- }
- } else {
- jars
- }
- }
-
- def dependentJarNames = dependentJars.getFiles.map(_.getName).filter(_.endsWith(".jar"))
- override def manifestClassPath = Some(dependentJarNames.map { "libs/" + _ }.mkString(" "))
-
- def distName = (artifactID + "-" + projectVersion.value)
- def distPath = "dist" / distName ##
-
- def configPath = "config" ##
- def configOutputPath = distPath / "config"
-
- def binPath = "bin" ##
- def binOutputPath = distPath / "bin"
-
- def distZipName = {
- "%s-%s.zip".format(artifactID, projectVersion.value)
- }
-
- lazy val packageDistTask = task {
- distPath.asFile.mkdirs()
- (distPath / "libs").asFile.mkdirs()
- binOutputPath.asFile.mkdirs()
- configOutputPath.asFile.mkdirs()
-
- FileUtilities.copyFlat(List(jarPath), distPath, log).left.toOption orElse
- FileUtilities.copyFlat(dependentJars.get, distPath / "libs", log).left.toOption orElse
- FileUtilities.copy((configPath ***).get, configOutputPath, log).left.toOption orElse
- FileUtilities.copy((binPath ***).get, binOutputPath, log).left.toOption orElse
- FileUtilities.zip((("dist" / distName) ##).get, "dist" / distZipName, true, log)
- None
- }
-
- val PackageDistDescription = "Creates a deployable zip file with dependencies, config, and scripts."
- lazy val packageDist = packageDistTask dependsOn(`package`, `test`) describedAs PackageDistDescription
-
- val cleanDist = cleanTask("dist" ##) describedAs("Erase any packaged distributions.")
- override def cleanAction = super.cleanAction dependsOn(cleanDist)
-
- override def javaCompileOptions = super.javaCompileOptions ++
- List(JavaCompileOption("-source"), JavaCompileOption("1.5"))
- }
-
- class KafkaExamplesProject(info: ProjectInfo) extends DefaultProject(info)
- with IdeaProject
- with CoreDependencies {
- val examplesPackageAction = packageAllAction
- val dependsOnCore = core
- //The issue is going from log4j 1.2.14 to 1.2.15, the developers added some features which required
- // some dependencies on various sun and javax packages.
- override def ivyXML =
- <dependencies>
- <exclude module="javax"/>
- <exclude module="jmxri"/>
- <exclude module="jmxtools"/>
- <exclude module="mail"/>
- <exclude module="jms"/>
- </dependencies>
-
- override def artifactID = "kafka-java-examples"
- override def filterScalaJars = false
- }
-
- class KafkaPerfProject(info: ProjectInfo) extends DefaultProject(info)
- with IdeaProject
- with CoreDependencies {
- val perfPackageAction = packageAllAction
- val dependsOnCore = core
- //The issue is going from log4j 1.2.14 to 1.2.15, the developers added some features which required
- // some dependencies on various sun and javax packages.
- override def ivyXML =
- <dependencies>
- <exclude module="javax"/>
- <exclude module="jmxri"/>
- <exclude module="jmxtools"/>
- <exclude module="mail"/>
- <exclude module="jms"/>
- </dependencies>
-
- override def artifactID = "kafka-perf"
- override def filterScalaJars = false
- }
-
- class ContribProject(info: ProjectInfo) extends ParentProject(info) with IdeaProject {
- lazy val hadoopProducer = project("hadoop-producer", "hadoop producer",
- new HadoopProducerProject(_), core)
- lazy val hadoopConsumer = project("hadoop-consumer", "hadoop consumer",
- new HadoopConsumerProject(_), core)
-
- val producerPackageAction = hadoopProducer.producerPackageAction
- val consumerPackageAction = hadoopConsumer.consumerPackageAction
-
- class HadoopProducerProject(info: ProjectInfo) extends DefaultProject(info)
- with IdeaProject
- with CoreDependencies {
- val producerPackageAction = packageAllAction
- override def ivyXML =
- <dependencies>
- <exclude module="netty"/>
- <exclude module="javax"/>
- <exclude module="jmxri"/>
- <exclude module="jmxtools"/>
- <exclude module="mail"/>
- <exclude module="jms"/>
- </dependencies>
-
- val avro = "org.apache.avro" % "avro" % "1.4.1"
- val jacksonCore = "org.codehaus.jackson" % "jackson-core-asl" % "1.5.5"
- val jacksonMapper = "org.codehaus.jackson" % "jackson-mapper-asl" % "1.5.5"
- }
-
- class HadoopConsumerProject(info: ProjectInfo) extends DefaultProject(info)
- with IdeaProject
- with CoreDependencies {
- val consumerPackageAction = packageAllAction
- override def ivyXML =
- <dependencies>
- <exclude module="netty"/>
- <exclude module="javax"/>
- <exclude module="jmxri"/>
- <exclude module="jmxtools"/>
- <exclude module="mail"/>
- <exclude module="jms"/>
- </dependencies>
-
- val jodaTime = "joda-time" % "joda-time" % "1.6"
- val httpclient = "commons-httpclient" % "commons-httpclient" % "3.1"
- }
- }
-
- trait TestDependencies {
- val easymock = "org.easymock" % "easymock" % "3.0" % "test"
- val junit = "junit" % "junit" % "4.1" % "test"
- val scalaTest = "org.scalatest" % "scalatest" % "1.2" % "test"
- }
-
- trait CoreDependencies {
- val log4j = "log4j" % "log4j" % "1.2.15"
- val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
- }
-
-}
+//import sbt._
+//
+//class KafkaProject(info: ProjectInfo) extends ParentProject(info) with IdeaProject {
+// lazy val core = project("core", "core-kafka", new CoreKafkaProject(_))
+// lazy val examples = project("examples", "java-examples", new KafkaExamplesProject(_), core)
+// lazy val perf = project("perf", "perf", new KafkaPerfProject(_), core)
+// lazy val contrib = project("contrib", "contrib", new ContribProject(_))
+//
+// lazy val releaseZipTask = core.packageDistTask
+//
+// val releaseZipDescription = "Compiles every sub project, runs unit tests, creates a deployable release zip file with dependencies, config, and scripts."
+// lazy val releaseZip = releaseZipTask dependsOn(core.corePackageAction, core.test, examples.examplesPackageAction, perf.perfPackageAction,
+// contrib.producerPackageAction, contrib.consumerPackageAction) describedAs releaseZipDescription
+//
+// class CoreKafkaProject(info: ProjectInfo) extends DefaultProject(info)
+// with IdeaProject with CoreDependencies with TestDependencies {
+// val corePackageAction = packageAllAction
+//
+// //The issue is going from log4j 1.2.14 to 1.2.15, the developers added some features which required
+// // some dependencies on various sun and javax packages.
+// override def ivyXML =
+// <dependencies>
+// <exclude module="javax"/>
+// <exclude module="jmxri"/>
+// <exclude module="jmxtools"/>
+// <exclude module="mail"/>
+// <exclude module="jms"/>
+// </dependencies>
+//
+// override def repositories = Set(ScalaToolsSnapshots, "JBoss Maven 2 Repository" at "http://repository.jboss.com/maven2",
+// "Oracle Maven 2 Repository" at "http://download.oracle.com/maven", "maven.org" at "http://repo2.maven.org/maven2/")
+//
+// override def artifactID = "kafka"
+// override def filterScalaJars = false
+//
+// // build the executable jar's classpath.
+// // (why is it necessary to explicitly remove the target/{classes,resources} paths? hm.)
+// def dependentJars = {
+// val jars =
+// publicClasspath +++ mainDependencies.scalaJars --- mainCompilePath --- mainResourcesOutputPath
+// if (jars.get.find { jar => jar.name.startsWith("scala-library-") }.isDefined) {
+// // workaround bug in sbt: if the compiler is explicitly included, don't include 2 versions
+// // of the library.
+// jars --- jars.filter { jar =>
+// jar.absolutePath.contains("/boot/") && jar.name == "scala-library.jar"
+// }
+// } else {
+// jars
+// }
+// }
+//
+// def dependentJarNames = dependentJars.getFiles.map(_.getName).filter(_.endsWith(".jar"))
+// override def manifestClassPath = Some(dependentJarNames.map { "libs/" + _ }.mkString(" "))
+//
+// def distName = (artifactID + "-" + projectVersion.value)
+// def distPath = "dist" / distName ##
+//
+// def configPath = "config" ##
+// def configOutputPath = distPath / "config"
+//
+// def binPath = "bin" ##
+// def binOutputPath = distPath / "bin"
+//
+// def distZipName = {
+// "%s-%s.zip".format(artifactID, projectVersion.value)
+// }
+//
+// lazy val packageDistTask = task {
+// distPath.asFile.mkdirs()
+// (distPath / "libs").asFile.mkdirs()
+// binOutputPath.asFile.mkdirs()
+// configOutputPath.asFile.mkdirs()
+//
+// FileUtilities.copyFlat(List(jarPath), distPath, log).left.toOption orElse
+// FileUtilities.copyFlat(dependentJars.get, distPath / "libs", log).left.toOption orElse
+// FileUtilities.copy((configPath ***).get, configOutputPath, log).left.toOption orElse
+// FileUtilities.copy((binPath ***).get, binOutputPath, log).left.toOption orElse
+// FileUtilities.zip((("dist" / distName) ##).get, "dist" / distZipName, true, log)
+// None
+// }
+//
+// val PackageDistDescription = "Creates a deployable zip file with dependencies, config, and scripts."
+// lazy val packageDist = packageDistTask dependsOn(`package`, `test`) describedAs PackageDistDescription
+//
+// val cleanDist = cleanTask("dist" ##) describedAs("Erase any packaged distributions.")
+// override def cleanAction = super.cleanAction dependsOn(cleanDist)
+//
+// override def javaCompileOptions = super.javaCompileOptions ++
+// List(JavaCompileOption("-source"), JavaCompileOption("1.5"))
+// }
+//
+// class KafkaExamplesProject(info: ProjectInfo) extends DefaultProject(info)
+// with IdeaProject
+// with CoreDependencies {
+// val examplesPackageAction = packageAllAction
+// val dependsOnCore = core
+// //The issue is going from log4j 1.2.14 to 1.2.15, the developers added some features which required
+// // some dependencies on various sun and javax packages.
+// override def ivyXML =
+// <dependencies>
+// <exclude module="javax"/>
+// <exclude module="jmxri"/>
+// <exclude module="jmxtools"/>
+// <exclude module="mail"/>
+// <exclude module="jms"/>
+// </dependencies>
+//
+// override def artifactID = "kafka-java-examples"
+// override def filterScalaJars = false
+// }
+//
+// class KafkaPerfProject(info: ProjectInfo) extends DefaultProject(info)
+// with IdeaProject
+// with CoreDependencies {
+// val perfPackageAction = packageAllAction
+// val dependsOnCore = core
+// //The issue is going from log4j 1.2.14 to 1.2.15, the developers added some features which required
+// // some dependencies on various sun and javax packages.
+// override def ivyXML =
+// <dependencies>
+// <exclude module="javax"/>
+// <exclude module="jmxri"/>
+// <exclude module="jmxtools"/>
+// <exclude module="mail"/>
+// <exclude module="jms"/>
+// </dependencies>
+//
+// override def artifactID = "kafka-perf"
+// override def filterScalaJars = false
+// }
+//
+// class ContribProject(info: ProjectInfo) extends ParentProject(info) with IdeaProject {
+// lazy val hadoopProducer = project("hadoop-producer", "hadoop producer",
+// new HadoopProducerProject(_), core)
+// lazy val hadoopConsumer = project("hadoop-consumer", "hadoop consumer",
+// new HadoopConsumerProject(_), core)
+//
+// val producerPackageAction = hadoopProducer.producerPackageAction
+// val consumerPackageAction = hadoopConsumer.consumerPackageAction
+//
+// class HadoopProducerProject(info: ProjectInfo) extends DefaultProject(info)
+// with IdeaProject
+// with CoreDependencies {
+// val producerPackageAction = packageAllAction
+// override def ivyXML =
+// <dependencies>
+// <exclude module="netty"/>
+// <exclude module="javax"/>
+// <exclude module="jmxri"/>
+// <exclude module="jmxtools"/>
+// <exclude module="mail"/>
+// <exclude module="jms"/>
+// </dependencies>
+//
+// val avro = "org.apache.avro" % "avro" % "1.4.1"
+// val jacksonCore = "org.codehaus.jackson" % "jackson-core-asl" % "1.5.5"
+// val jacksonMapper = "org.codehaus.jackson" % "jackson-mapper-asl" % "1.5.5"
+// }
+//
+// class HadoopConsumerProject(info: ProjectInfo) extends DefaultProject(info)
+// with IdeaProject
+// with CoreDependencies {
+// val consumerPackageAction = packageAllAction
+// override def ivyXML =
+// <dependencies>
+// <exclude module="netty"/>
+// <exclude module="javax"/>
+// <exclude module="jmxri"/>
+// <exclude module="jmxtools"/>
+// <exclude module="mail"/>
+// <exclude module="jms"/>
+// </dependencies>
+//
+// val jodaTime = "joda-time" % "joda-time" % "1.6"
+// val httpclient = "commons-httpclient" % "commons-httpclient" % "3.1"
+// }
+// }
+//
+// trait TestDependencies {
+// val easymock = "org.easymock" % "easymock" % "3.0" % "test"
+// val junit = "junit" % "junit" % "4.1" % "test"
+// val scalaTest = "org.scalatest" % "scalatest" % "1.2" % "test"
+// }
+//
+// trait CoreDependencies {
+// val log4j = "log4j" % "log4j" % "1.2.15"
+// val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
+// }
+//
+//}
diff --git a/project/plugins/Plugins.scala b/project/plugins/Plugins.scala
deleted file mode 100644
index 6938e30..0000000
--- a/project/plugins/Plugins.scala
+++ /dev/null
@@ -1,6 +0,0 @@
-import sbt._
-
-class Plugins(info: ProjectInfo) extends PluginDefinition(info) {
- val repo = "GH-pages repo" at "http://mpeltonen.github.com/maven/"
- val idea = "com.github.mpeltonen" % "sbt-idea-plugin" % "0.1-SNAPSHOT"
-}
diff --git a/sbt b/sbt
index 7d8b41e..657e990 100755
--- a/sbt
+++ b/sbt
@@ -1 +1,2 @@
-java -Xmx1024M -XX:MaxPermSize=512m -jar `dirname $0`/lib/sbt-launch.jar "$@"
+java -Xmx1024M -XX:MaxPermSize=512m -jar `dirname $0`/sbt-launch.jar "$@"
+
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-133:
--------------------------------
Fix Version/s: 0.8
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6, 0.8
> Reporter: Neha Narkhede
> Labels: patch
> Fix For: 0.8
>
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456309#comment-13456309 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
+1 for this. Funny, it looks like it has been exactly 365 days since the issue was opened and a bit over 6 months since the last comment. KAFKA-134 is still blocking... :( [~jkreps], [~charmalloc], & co, any chance of committing KAFKA-134 to unblock this issue (9 votes)?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Jay Kreps (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134320#comment-13134320 ]
Jay Kreps commented on KAFKA-133:
---------------------------------
Josh, you are seriously my hero. Drinks are owed.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Sam Meder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474757#comment-13474757 ]
Sam Meder commented on KAFKA-133:
---------------------------------
One issue with doing this for the 0.8 branch is that it contains ~3 dependencies that are checked into the kafka source itself...
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Chris Riccomini (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117392#comment-13117392 ]
Chris Riccomini commented on KAFKA-133:
---------------------------------------
Hey Guys,
Is there a maven repo for Kafka at this point? :)
I sure could use it if there is one.
Cheers,
Chris
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Reporter: Neha Narkhede
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Thomas Dudziak (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222510#comment-13222510 ]
Thomas Dudziak commented on KAFKA-133:
--------------------------------------
Also, instead of having sbt (and pom) sections that exclude log4j 1.2.15's pulled-in dependency, you could simply update to log4j 1.2.16
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496321#comment-13496321 ]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
>> Custom zkclient jar... maybe a Kafka developer in the know can jump in?
That's because we modified one of the zk client APIs to expose the stat object returned from the underlying zookeeper APIs. But after that, zkclient was never published to Maven.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496860#comment-13496860 ]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
>> So is the blocker for this issue the fact that there is a custom zkclient?
I believe so.
>> Should the modified API be provided as a patch to the original zkclient?
It is already checked into zkclient trunk
>> Should the zkclient maintainers be nudged to publish the new zkclient to a Maven repo?
Sure, please feel free to ping them.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134356#comment-13134356 ]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
Thanks for the patch Josh ! Well in time for 0.7 release.
Please could you attach the diff file here and also select the "grant it to Apache" option ? That way we can apply, test and accept the patch.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Jay Kreps (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504826#comment-13504826 ]
Jay Kreps commented on KAFKA-133:
---------------------------------
Hey Otis, that's awesome. Thanks for taking point on that and keeping the focus on this issue.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6, 0.8
> Reporter: Neha Narkhede
> Labels: patch
> Fix For: 0.8
>
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495769#comment-13495769 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
Coda Hale metrics does seem to be in Maven repo already, see: http://mvnrepository.com/artifact/com.yammer.metrics
Custom zkclient jar... maybe a Kafka developer in the know can jump in?
Maybe this jar could be included/hidden in one of the Kafka jars, so it is not treated as external dependencies?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Pierre-Yves Ritschard (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183402#comment-13183402 ]
Pierre-Yves Ritschard commented on KAFKA-133:
---------------------------------------------
The pom.xml contained in this gist, coupled with the artifact built by the source contents of the kafka-0.7-incubating-src archive can be deployed to a maven repository and ease things for java clients.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Jay Kreps (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105670#comment-13105670 ]
Jay Kreps commented on KAFKA-133:
---------------------------------
Josh, you are my hero.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Reporter: Neha Narkhede
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (KAFKA-133) Publish kafka jar to a public
maven repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495769#comment-13495769 ]
Otis Gospodnetic edited comment on KAFKA-133 at 11/13/12 12:14 AM:
-------------------------------------------------------------------
Coda Hale metrics does seem to be in Maven repo already, see: http://mvnrepository.com/artifact/com.yammer.metrics
Though from KAFKA-585 it looks like there may be a dependency on Metrics 3.*, which is not in any Maven repo yet.
Custom zkclient jar... maybe a Kafka developer in the know can jump in?
Maybe this jar could be included/hidden in one of the Kafka jars, so it is not treated as external dependencies?
was (Author: otis):
Coda Hale metrics does seem to be in Maven repo already, see: http://mvnrepository.com/artifact/com.yammer.metrics
Custom zkclient jar... maybe a Kafka developer in the know can jump in?
Maybe this jar could be included/hidden in one of the Kafka jars, so it is not treated as external dependencies?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498597#comment-13498597 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
FYI just emailed Stefan asking if zkclient 0.2 could be cut and published in Maven. He replied a few minutes later from a cab and CCed his colleague asking him to do this, so if stars align, you may see zkclient 0.2 out and you can remove it from Kafka.
And then I really really hope you can publish Kafka to a Maven repo! :)
Questions/comments:
* How come this is not Fix Version 0.8? Should it not be? Is it not planned for the upcoming 0.8?
* Nobody is assigned. Is it known who will do this?
* It looks like KAFKA-134 is marked as blocker, but it's also not assigned and is not set for 0.8...?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178829#comment-13178829 ]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
Patricio,
This ticket is blocked on KAFKA-134. Once that is resolved, I believe this ticket will be easier to resolve.
Thanks,
Neha
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (KAFKA-133) Publish kafka jar to a public
maven repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495769#comment-13495769 ]
Otis Gospodnetic edited comment on KAFKA-133 at 11/13/12 12:45 AM:
-------------------------------------------------------------------
Coda Hale metrics does seem to be in Maven repo already, see: http://mvnrepository.com/artifact/com.yammer.metrics
Though from KAFKA-585 it looks like there may be a dependency on Metrics 3.*, which is not in any Maven repo yet.
Custom zkclient jar... maybe a Kafka developer in the know can jump in?
Maybe this jar could be included/hidden in one of the Kafka jars, so it is not treated as external dependencies?
Oh, is that zkclient Stefan's zkclient? This one: http://mvnrepository.com/artifact/com.github.sgroschupf/zkclient/0.1 but locally modified, jarred, and stuck in svn?
Maybe we could instead provide a patch for zkclient and get zkclient maintainer(s) to apply it? I knows Stefan personally and could bug him about it.... he is a busy CEO these days, but maybe somebody else on his team could get this done.
was (Author: otis):
Coda Hale metrics does seem to be in Maven repo already, see: http://mvnrepository.com/artifact/com.yammer.metrics
Though from KAFKA-585 it looks like there may be a dependency on Metrics 3.*, which is not in any Maven repo yet.
Custom zkclient jar... maybe a Kafka developer in the know can jump in?
Maybe this jar could be included/hidden in one of the Kafka jars, so it is not treated as external dependencies?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Joshua Hartman (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134383#comment-13134383 ]
Joshua Hartman commented on KAFKA-133:
--------------------------------------
I came into Mountain View today on a loooong train ride and my internet died right after I posted this. I wanted to say that it wasn't quite ready, but that we should sit down today and go through this so we can perfect it for kafka's long term needs.
Chris Riccomini reminded me about this on Friday and I promised myself I would finish it over the weekend - I think I'm about 3 weeks overdue.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-133:
--------------------------------
Affects Version/s: 0.8
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6, 0.8
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Sam Meder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495751#comment-13495751 ]
Sam Meder commented on KAFKA-133:
---------------------------------
The third party dependencies that I am aware of are:
com.yammer.metrics, metrics-core
com.yammer.metrics, metrics-annotation
and a custom zkclient jar
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105592#comment-13105592 ]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
Thanks for picking this up. Also, do you mind filing another JIRA for the sbt 0.10.1 upgrade ?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Reporter: Neha Narkhede
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Joshua Hartman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105588#comment-13105588 ]
Joshua Hartman commented on KAFKA-133:
--------------------------------------
I did this last night for one of our other projects, Norbert.
If I upgrade Kafka to sbt 0.10.1, I should be able to do this. Will also write a blog post so other projects know how to do this with maven.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Reporter: Neha Narkhede
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495394#comment-13495394 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
Maybe the thing to do then is to help owners of those projects Kafka depends on get their stuff into Maven, starting by opening tickets in their issue tracker.
[~meder@mcs.anl.gov] or [~smeder] - which dependencies are those specifically?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496843#comment-13496843 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
Thanks Neha.
So is the blocker for this issue the fact that there is a custom zkclient?
Should the modified API be provided as a patch to the original zkclient?
Should the zkclient maintainers be nudged to publish the new zkclient to a Maven repo?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495770#comment-13495770 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
I noticed Fix Version is not set, but if you look at https://issues.apache.org/jira/browse/KAFKA#selectedTab=com.atlassian.jira.plugin.system.project%3Apopularissues-panel you'll see this is THE most popular Kafka issue.
Shouldn't this be set to 0.8, so it gets done for/with the upcoming release?
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Pierre-Yves Ritschard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496063#comment-13496063 ]
Pierre-Yves Ritschard commented on KAFKA-133:
---------------------------------------------
the zkclient dep moved to maven a while back it is not modified IIRC
On Tue, Nov 13, 2012 at 1:45 AM, Otis Gospodnetic (JIRA)
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506824#comment-13506824 ]
Otis Gospodnetic commented on KAFKA-133:
----------------------------------------
There you have it:
zkclient 0.2:
http://search.maven.org/#artifactdetails%7Ccom.101tec%7Czkclient%7C0.2%7Cjar
metrics 2.2.0:
http://search.maven.org/#artifactdetails%7Ccom.yammer.metrics%7Cmetrics-parent%7C2.2.0%7Cpom
This is now the most popular Kafka issue by far!
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6, 0.8
> Reporter: Neha Narkhede
> Labels: patch
> Fix For: 0.8
>
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Neha Narkhede (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499940#comment-13499940 ]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
* How come this is not Fix Version 0.8? Should it not be? Is it not planned for the upcoming 0.8?
Just changed the affected version to 0.8
* Nobody is assigned. Is it known who will do this?
Anyone who is interested can pick this up. Feel free to assign this to yourself.
* It looks like KAFKA-134 is marked as blocker, but it's also not assigned and is not set for 0.8...?
KAFKA-134 is required only to be able to publish to maven using an sbt command. For 0.8, if that is not ready, we can manually publish it. All the assignee would do in this case, is figure out the procedure to get this done and post it here. One of the committers can help roll the ball.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6, 0.8
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (KAFKA-133) Publish kafka jar to a
public maven repository
Posted by "Alan Cabrera (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105604#comment-13105604 ]
Alan Cabrera edited comment on KAFKA-133 at 9/29/11 5:35 PM:
-------------------------------------------------------------
I need to state the obvious, because I am a mentor, but while it's good to get this machinery working, this project cannot actually publish any artifacts until its first official release.
was (Author: maguro):
I need to state the obvious, because I am a mentor, but while it's good to get this machinery working, this project cannot actually publish any artifacts yet.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Reporter: Neha Narkhede
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Chris Aniszczyk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471741#comment-13471741 ]
Chris Aniszczyk commented on KAFKA-133:
---------------------------------------
bump... +1
Can this be done? We're looking to consume Kafka...
At least to the Sonatype OSS repo or somewhere?
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Neha Narkhede
> Labels: patch
> Attachments: pom.xml
>
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven
repository
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105604#comment-13105604 ]
Alan Cabrera commented on KAFKA-133:
------------------------------------
I need to state the obvious, because I am a mentor, but while it's good to get this machinery working, this project cannot actually publish any artifacts yet.
> Publish kafka jar to a public maven repository
> ----------------------------------------------
>
> Key: KAFKA-133
> URL: https://issues.apache.org/jira/browse/KAFKA-133
> Project: Kafka
> Issue Type: Improvement
> Reporter: Neha Narkhede
>
> The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2.
> Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo.
> In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira