-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish to Maven Central #194
Comments
Why is it better to be on Sonatype OSS than maven.twttr? |
Because it automatically syncs to Maven Central. I'm slowly weaning Twitter off of maven.twttr.com for most things and having artifacts published to Maven Central instead. |
Neat, good to know. |
Filed the ticket: https://issues.sonatype.org/browse/OSSRH-4607 |
Looks fine, would be great to have this change coincide moving to Maven :) To sync to maven central, we need spruce up our POM most likely with extra metadata: |
So, has anything been published yet? |
@caniszczyk seems like the last release was end of Aug, 2013 -- any chance of cutting a new release and publishing it to sonatype? |
@jpinner Yes. We're working on scheduling it now. |
any updates? |
I think the idea is that openzipkin will drive artifact publication @rtyler can invite you to the org as well! |
The https://github.com/openzipkin org includes a zipkin-core team which has jpinner in it now too. The plan is to publish artifacts to https://bintray.com/openzipkin/maven after merging some in-flight sbt-bintray work Lookout built. |
Just to touch this again. Inside Twitter, maven central is the preferred repo, and our pants 3rdparty will only look at that and https://maven.twttr.com/ I can manually push to the latter until central sync is supported. That would be ideally something that's already published to bintray. Once something is published somewhere, I can move twitter onto openzipkin, which would be very sweet. |
@rtyler @eirslett @michaelsembwever @kristofa @jamescway (think this is openzipkin founding parents)... So, are you thinking com.github.openzipkin:zipkin-whatev? Once we decide on group id, I can start the sonatype ticket. |
Fantastic, thanks a lot! :-) |
@adriancole sounds good to me, can you get twitter to just point zipkin.io at GitHub's nameservers for CNAME purposes? |
@rtyler I just added you to have manage products ability on godaddy, so
lemme know if that didn't work.
|
https://issues.sonatype.org/browse/OSSRH-16669 I'd like a backup.. @eirslett @michaelsembwever @abesto @kristofa @aasta .. can one or more of you register on https://issues.sonatype.org and add a comment ^^ with your username? |
soo.. we did this, and it didn't even take 3 years! https://repo1.maven.org/maven2/io/zipkin/zipkin-common/1.2.1/ |
Makes sure all maven artifacts are prefixed with zipkin
I discussed with @franklinhu on creating a Sonatype OSS account:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
This would allow us to publish artifacts directly to Maven Central and be good open source citizens.
The text was updated successfully, but these errors were encountered: