[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644742#comment-13644742
]
Alex Gray commented on KAFKA-133:
---------------------------------
Silly question, but I just downloaded 0.8 branch and I see no pom.xml.
I would like to locally build kafka and publish to our private local maven repo.
Is this currently possible? Do I have to do something for the pom.xml to get
generated.
Sorry for the newbie question.
I noticed that when I run ./sbt publish-local, the artifacts get pushed to my
local repo:
~/.ivy2/local/org.apache/contrib_2.8.0
~/.ivy2/local/org.apache/kafka_2.8.0
I would like to publish to our private local maven repo (which just so happens
to be in S3), but I'm used to modifying a pom.xml to add the required
plugins/repoID's/etc/etc/, hence the question on where the pom.xml is.
Thanks!
> 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: KAFKA-133.patch, 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
