Publishing to Maven Central

[bpholt]

The README says

The code is not yet being deployed to Maven central (we're working on that!), so you'll have to build your own version.

What's the status of deploying to Maven Central? Is there anything I can help with?

I'm also working on adding modules to some other libraries that would depend on this one, which need publicly available artifacts for their CI builds. Until this library is publicly published (and something like #7 is merged), I was thinking about publishing our build under another group ID (probably to my company's Maven repository on Bintray). Do you have any concerns with that? Should I also rename the Java packages, or is it good enough to use different Maven coordinates for the jar?

[ashleymercer]

Hi @bpholt

Sorry for the radio silence - obviously this year has been a bit unusual, but prompted by #10 I'm aiming to clean a few things up with this repo.

Yes if you have experience of deploying to Maven Central that would be very much appreciated. I had some contact before with the opentracing-java maintainers which I'll attempt to resurrect, they should have the necessary keys to deploy under the right Maven coordinates (or be able to give us our own keys to do so).

I don't have an objection to you publishing under different Maven co-ordinates but keeping the package names the same: changing imports everywhere would just be a nuisance, and given the license, I'm not sure there's much I could do to stop you anyway - but thanks for asking :)