-
Notifications
You must be signed in to change notification settings - Fork 41
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
New Java install instructions #196
Comments
@paddybyers @psolstice I do not think the instructions for usage of the library for users for Java & Android is right and needs your input as I do not have sufficient experience with Java to do this. Firstly, if you look at our README for the Java lib itself, it talks about "Using the library..", then Dependencies, then Building, then Installation (it also used to talk about Tests, I moved this). The Using section tells the user to read the main documentation at https://www.ably.io/documentation. If you look at the main usage documentation (choose Java in the lang nav) for Realtime and for REST, it loosely mentions Gradle, but has no mention of Android. Then if I go to https://bintray.com/ably-io/ably which is the bintray link, there is now
Anyone looking to use Ably in an Android or JRE environment, IMHO, would rightfully be quite confused. We need to please think about making this more user friendly for users in our documentation and in our READMEs, and within JFrog. See https://github.com/ably/ably-ruby, https://www.ably.io/documentation/realtime/usage (choose Ruby lang) and https://rubygems.org/gems/ably as a comparison. |
The first thing to sort out is the android project and package. Currently android users are still using the java library, which they've been doing since before the restructure, but once we have an android library we should export that. The package should be renamed to
The first section should be the Installation section, which says what the gradle dependency is. This should be stated separately, as it is now, for Android and java. Then the "Using the Realtime API" and finally the bits about building from source.
This is because, right now, there isn't a separate Android package, so the java binary is used for both Android and java, and the gradle dependency is the same. But we should fix the Android package and update that section of the docs.
yes
We should populate the package metadata fields in bintray. The project itself has a readme.
This will be taken care of with the updates for the android package once that's been created. As I noted yesterday, this is just obsolete and needs to be removed. |
@paddybyers @psolstice as far as I can tell this is still not done correctly.
|
Hopefully these are all now addressed for ably-java and ably-android. I've not done java-websocket yet. Irritatingly, bintray doesn't support gtihub markdown, so the syntaxt-highlighted code blocks don't work in the readme and they break the formatting. So I've just uploaded a shortened readme for the packages which links to the full one on github. |
The Java-WebSocket readme had the same markdown issues so I added a shortform readme directly to bintray. Unfortuately there seems to be a problem with the Bintray shields, which were all working fine earlier today :( |
This has been done now |
See ably/ably-java#171 and ably/ably-java#161
The text was updated successfully, but these errors were encountered: