Have tagged versions available in Maven Central

Question

Have tagged versions available in Maven Central

kiview opened this issue 7 years ago · 7 comments

Although Jitpack is a good solution, a mature library should provide their artifacts in Maven Central as well.

Answer 1 · 2017-07-25T06:49:05.000Z

It may be much easier to publish to Bintray: https://github.com/bintray/gradle-bintray-plugin

Answer 2 · 2017-07-25T08:11:35.000Z

That's true, but I was planning on having it in the same Maven Central group as testcontainers-java. Also I think having it in Bintray isn't that much of an improvement over jitpack.io, since it isn't a Maven/Gradle default?

Answer 3 · 2017-07-25T08:29:28.000Z

What do you mean "default"? Gradle has no default central repository. It is true, that the majority of examples use mavenCentral(), but it is similarly easy to use jcenter() in gradle script. It is HUGE improvement over jitpack, as it gives clear versioning to all users.

Besides, although I have not done this, but people say it is MUCH easier to publish to Maven Central via Bintray.

Answer 4 · 2017-07-26T14:09:40.000Z

mavenCentral() is still the default for Maven, that's the reason. But I definitely see your point. Still like to release it in a similar fashion to testcontainers-java.

Answer 5 · 2017-07-26T14:15:27.000Z

This may be of help: https://bintray.com/docs/usermanual/uploads/uploads_syncingwiththirdpartyplatforms.html

Answer 6 · 2017-07-26T15:33:05.000Z

Btw. would it help to have tagged version in Github, so you can depend on tagged versions using Jitpack?

Answer 7 · 2018-01-29T13:02:49.000Z

I've added a tagged release for the current version:
testCompile 'com.github.testcontainers:testcontainers-spock:1.0.0-tc1.6.0'

Since we'll likely move this repo into the testcontainers-java repo (see testcontainers/testcontainers-java#564), I won't do further work on this issue in this project itself.