Apollo-android: Upload release artifacts to Maven Central?

[brockgibson]

I am looking to integrate apollo-android into an application in a development environment that has integration with maven central but not jcenter. Would it be possible to have all apollo-android (e.g. apollo-runtime, ...) get deployed to maven central in addition to jcenter? The last release I see showing is 0.4.1.

I do see releases pushed under a tab called "Spring Plugins" which seems a little odd and they are not available at https://repo.maven.apache.org/maven2 either.

[digitalbuddha]

you're right there's a problem with the publishing. We will correct. In the meantime use jcenter

[martinbonnin]

Even jcenter seems to lag sometimes ? I recently had to include bintray explicitely (and not jcenter)

maven {
    url 'http://dl.bintray.com/apollographql/android'
}

I'm not an expert at this but it certainly feels a bit weird

[aoudiamoncef]

Hello,
You could easily sync release artifacts to maven central from the UI using the API.
https://bintray.com/docs/api/#_sync_version_artifacts_to_maven_central

[gabrielittner]

Any updates on this?

[adghrera]

Any updates?

[martinbonnin]

Another reason to switch to mavenCentral would be to have proper plugin marker support, I can't get them to be promoted to jcenter.

I might give it a shot in the coming days/weeks. Still figuring out whether to use bintray sync or just promote the SNAPSHOTs that we are already uploading to OSS.

[martinbonnin]

Plugin markers are now uploaded to jcenter too. See https://github.com/apollographql/apollo-android/pull/2001.

Is mavenCentral really needed ? Now that I think about it, I kind of like having a single source of truth in jcenter. What are the pros of syncing to mavenCentral ?

[bbc2]

Maven Central being the default repository in Maven, having apollo-android there would enable users to get it without having to tweak repositories.

[martinbonnin]

Maven Central being the default repository in Maven

Are you using apollo with maven (as in the maven build tool) ? Since apollo uses a gradle plugin I was expecting everyone to use gradle and there jcenter() and mavenCentral() both have to be explicitely added if I'm not mistaken.

For the record, I'm not against adding mavenCentral, I'm trying to understand what the use case exactly before committing to supporting yet another repo.

[bbc2]

Yes, we build an API client library with the Gradle plugin, but that library is then used by various projects, including some that are built with Maven. The transitive dependency they have to download, currently from jcenter, is com.apollographql.apollo:apollo-runtime. So, for us at least, being able to get that artifact from Maven Central (and also for our users) would be great!

[aoudiamoncef]

Any updates?

[martinbonnin]

@aoudiamoncef artifacts shouldn't be in mavenCentral yet. https://repo1.maven.org/maven2/com/apollographql/apollo/ only contains old versions.
There are some snapshots at https://oss.sonatype.org/content/repositories/snapshots/com/apollographql/apollo/ but I don't recommend using snapshots in production.
If you can find them, please let us know at what url as it sounds weird.

[aoudiamoncef]

I'm sorry, I commented the wrong issue 🙏. I was talking about #2099.

[martinbonnin]

Releases starting with 2.2.0 should be both on MavenCentral and JCenter:

https://repo1.maven.org/maven2/com/apollographql/apollo/
https://jcenter.bintray.com/com/apollographql/apollo/

See https://github.com/apollographql/apollo-android/pull/2365