You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add connectionKey attribute missing from the Message object [\#630](https://github.com/ably/ably-java/pull/630) ([vzhikserg](https://github.com/vzhikserg)), fixing [\#614](https://github.com/ably/ably-java/issues/614)
10
+
- Improve error messages for channel attach when realtime is not active [\#627](https://github.com/ably/ably-java/pull/627) ([vzhikserg](https://github.com/vzhikserg)), fixing [\#594](https://github.com/ably/ably-java/issues/594)
11
+
- Add verbose logs in push notification related code [\#623](https://github.com/ably/ably-java/pull/623) ([QuintinWillison](https://github.com/QuintinWillison))
- Rest.publishBatch: support overloaded method that takes params [\#604](https://github.com/ably/ably-java/pull/604) ([SimonWoolf](https://github.com/SimonWoolf))
14
+
15
+
**Code Quality Improvements:**
16
+
17
+
- Refactor unit tests related to hosts and environmental fallbacks [\#629](https://github.com/ably/ably-java/pull/629) ([vzhikserg](https://github.com/vzhikserg)), fixing [\#628](https://github.com/ably/ably-java/issues/628)
18
+
- Move tests for EventEmitter to unit tests [\#626](https://github.com/ably/ably-java/pull/626) ([vzhikserg](https://github.com/vzhikserg))
19
+
- Adopt more Groovy conventions in Gradle scripts [\#625](https://github.com/ably/ably-java/pull/625) ([QuintinWillison](https://github.com/QuintinWillison))
20
+
- Gradle conform and reformat [\#624](https://github.com/ably/ably-java/pull/624) ([QuintinWillison](https://github.com/QuintinWillison))
21
+
- Fix param and return javadoc statements [\#622](https://github.com/ably/ably-java/pull/622) ([vzhikserg](https://github.com/vzhikserg))
22
+
- Make Ably version more robust [\#619](https://github.com/ably/ably-java/pull/619) ([vzhikserg](https://github.com/vzhikserg))
23
+
- Remove unnecessary calls to the toString method [\#617](https://github.com/ably/ably-java/pull/617) ([vzhikserg](https://github.com/vzhikserg))
- Convert tabs to spaces in all Java source files [\#610](https://github.com/ably/ably-java/pull/610) ([QuintinWillison](https://github.com/QuintinWillison))
- Remove redundant public keywords in the interfaces' definitions [\#608](https://github.com/ably/ably-java/pull/608) ([vzhikserg](https://github.com/vzhikserg))
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,13 +30,13 @@ Reference the library by including a compile dependency reference in your gradle
30
30
For [Java](https://bintray.com/ably-io/ably/ably-java/_latestVersion):
31
31
32
32
```
33
-
compile 'io.ably:ably-java:1.2.2'
33
+
compile 'io.ably:ably-java:1.2.3'
34
34
```
35
35
36
36
For [Android](https://bintray.com/ably-io/ably/ably-android/_latestVersion):
37
37
38
38
```
39
-
compile 'io.ably:ably-android:1.2.2'
39
+
compile 'io.ably:ably-android:1.2.3'
40
40
```
41
41
42
42
The library is hosted on the [Jcenter repository](https://bintray.com/ably-io/ably), so you need to ensure that the repo is referenced also; IDEs will typically include this by default:
@@ -616,15 +616,15 @@ Configuration of Run/Debug configurations for running the unit tests on Android
616
616
617
617
This library uses [semantic versioning](http://semver.org/). For each release, the following needs to be done:
618
618
619
-
1. Create a branch for the release, named like `release/1.2.2`
619
+
1. Create a branch for the release, named like `release/1.2.3`
620
620
2. Replace all references of the current version number with the new version number (check this file [README.md](./README.md) and [common.gradle](./common.gradle)) and commit the changes
621
621
3. Run [`github_changelog_generator`](https://github.com/skywinder/Github-Changelog-Generator) to update the [CHANGELOG](./CHANGELOG.md):
* But your mileage may vary as it can error. Perhaps more reliable is something like: `github_changelog_generator -u ably -p ably-java --since-tag v1.2.1 --output delta.md` and then manually merge the delta contents in to the main change log
* But your mileage may vary as it can error. Perhaps more reliable is something like: `github_changelog_generator -u ably -p ably-java --since-tag v1.2.2 --output delta.md` and then manually merge the delta contents in to the main change log
624
624
4. Commit [CHANGELOG](./CHANGELOG.md)
625
625
5. Make a PR against `main`
626
626
6. Once the PR is approved, merge it into `main`
627
-
7. Add a tag and push to origin - e.g.: `git tag v1.2.2 && git push origin v1.2.2`
627
+
7. Add a tag and push to origin - e.g.: `git tag v1.2.3 && git push origin v1.2.3`
628
628
8. Create the release on Github including populating the release notes (needed so JFrog can pull them in)
629
629
9. Assemble and Upload ([see below](#publishing-to-jcenter-and-maven-central) for details) - but the overall order to follow is:
630
630
1. Upload to Bintray and use the pushed tag, which will pull in the associated release notes
@@ -652,18 +652,18 @@ We publish to:
652
652
653
653
The `java` release process goes as follows:
654
654
655
-
* Go to the home page for the package; eg https://bintray.com/ably-io/ably/ably-java. Select Add a version, enter the new version such as "1.2.2" in name and save
655
+
* Go to the home page for the package; eg https://bintray.com/ably-io/ably/ably-java. Select Add a version, enter the new version such as "1.2.3" in name and save
656
656
* Run `./gradlew java:assembleRelease` locally to generate the files
657
-
* Open local relative folder in Finder, such as `./java/build/release/1.2.2/io/ably/ably-java/1.2.2`
658
-
* Go to the new version in JFrog Bintray; eg https://bintray.com/ably-io/ably/ably-java/1.2.2, then click on the link to upload via the UI in the "Upload files" section
657
+
* Open local relative folder in Finder, such as `./java/build/release/1.2.3/io/ably/ably-java/1.2.3`
658
+
* Go to the new version in JFrog Bintray; eg https://bintray.com/ably-io/ably/ably-java/1.2.3, then click on the link to upload via the UI in the "Upload files" section
659
659
* Drag in the files from Finder, just the `.jar` files and the `.pom` file. JFrog will fill in the "Target Path" box after you drop the files in. Click the "Upload" button.
660
660
* You will see a notice something like "4 unpublished files in your version. Will be deleted in 6 days and 22 hours. Publish all or Delete all unpublished files.", make sure you click "Publish all". Wait a few minutes and check that what's uploaded looks like what was uploaded for previous releases. The `maven-metadata` files are created by JFrog.
661
661
* Update the README text in Bintray (version number needs incrementing).
662
662
663
663
Similarly for the `android` release at https://bintray.com/ably-io/ably/ably-android:
664
664
665
665
* Run `./gradlew android:assembleRelease` locally to generate the files, and drag in the files in
0 commit comments