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) <j...@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 >
