Hi folks,
I tried to use the java client and it turns out io.ably:ably-java:1.1.5 depends on io.ably:Java-WebSocket:1.3.1 but that artifact is not in Maven central. Unless you have http://jcenter.bintray.com repository added to the POM, Maven can't find the dependency and the build fails. Please consider releasing the artifact to Maven Central.
On a related note - none of the 1.1.6 artifacts are in Maven central even though they have been published on jcenter on Nov 15. If you auto-sync with Maven Central perhaps you should check your process. If your strategy is to only use jcenter you should probably document that in a prominent place as most Java developers would expect your artifacts to be on Maven Central.
┆Issue is synchronized with this Jira Uncategorised by Unito
Hi folks,
I tried to use the java client and it turns out
io.ably:ably-java:1.1.5depends onio.ably:Java-WebSocket:1.3.1but that artifact is not in Maven central. Unless you havehttp://jcenter.bintray.comrepository added to the POM, Maven can't find the dependency and the build fails. Please consider releasing the artifact to Maven Central.On a related note - none of the
1.1.6artifacts are in Maven central even though they have been published on jcenter on Nov 15. If you auto-sync with Maven Central perhaps you should check your process. If your strategy is to only use jcenter you should probably document that in a prominent place as most Java developers would expect your artifacts to be on Maven Central.┆Issue is synchronized with this Jira Uncategorised by Unito