Skip to content
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

Closed
caniszczyk opened this issue Oct 29, 2012 · 19 comments
Closed

Publish to Maven Central #194

caniszczyk opened this issue Oct 29, 2012 · 19 comments

Comments

@caniszczyk
Copy link

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.

@mosesn
Copy link
Contributor

mosesn commented Oct 29, 2012

Why is it better to be on Sonatype OSS than maven.twttr?

@caniszczyk
Copy link
Author

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.

@mosesn
Copy link
Contributor

mosesn commented Oct 30, 2012

Neat, good to know.

@franklinhu
Copy link
Contributor

Filed the ticket: https://issues.sonatype.org/browse/OSSRH-4607
@caniszczyk can you sanity check that?

@caniszczyk
Copy link
Author

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:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement

@mauhiz
Copy link

mauhiz commented Apr 2, 2015

So, has anything been published yet?

@jpinner
Copy link

jpinner commented Jun 16, 2015

@caniszczyk seems like the last release was end of Aug, 2013 -- any chance of cutting a new release and publishing it to sonatype?

@smparkes
Copy link

@jpinner Yes. We're working on scheduling it now.

@jpinner
Copy link

jpinner commented Jul 7, 2015

any updates?

@codefromthecrypt
Copy link
Member

I think the idea is that openzipkin will drive artifact publication @rtyler can invite you to the org as well!

@codefromthecrypt
Copy link
Member

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.

@codefromthecrypt
Copy link
Member

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.

@codefromthecrypt
Copy link
Member

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

@codefromthecrypt
Copy link
Member

Twitter donated zipkin.io to us. @aasta has access to the godaddy stuff. I suspect we could use this for group id, etc? cc @eirslett @rtyler

@eirslett
Copy link
Contributor

Fantastic, thanks a lot! :-)
io.zipkin it is!

@rtyler
Copy link

rtyler commented Jul 17, 2015

@adriancole sounds good to me, can you get twitter to just point zipkin.io at GitHub's nameservers for CNAME purposes?

@codefromthecrypt
Copy link
Member

codefromthecrypt commented Jul 17, 2015 via email

@codefromthecrypt
Copy link
Member

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?

@codefromthecrypt
Copy link
Member

soo.. we did this, and it didn't even take 3 years!

https://repo1.maven.org/maven2/io/zipkin/zipkin-common/1.2.1/

codefromthecrypt pushed a commit that referenced this issue Jun 3, 2016
Makes sure all maven artifacts are prefixed with zipkin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants