Skip to content

Commit

Permalink
Update the README for 0.14.2.
Browse files Browse the repository at this point in the history
  • Loading branch information
jchambers committed Oct 21, 2020
1 parent e33e9b4 commit c16260a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,11 @@ If you use [Maven](http://maven.apache.org/), you can add Pushy to your project
<dependency>
<groupId>com.eatthepath</groupId>
<artifactId>pushy</artifactId>
<version>0.14.1</version>
<version>0.14.2</version>
</dependency>
```

If you don't use Maven (or something else that understands Maven dependencies, like Gradle), you can [download Pushy as a `.jar` file](https://github.com/jchambers/pushy/releases/download/pushy-0.14.1/pushy-0.14.1.jar) and add it to your project directly. You'll also need to make sure you have Pushy's runtime dependencies on your classpath. They are:
If you don't use Maven (or something else that understands Maven dependencies, like Gradle), you can [download Pushy as a `.jar` file](https://github.com/jchambers/pushy/releases/download/pushy-0.14.2/pushy-0.14.2.jar) and add it to your project directly. You'll also need to make sure you have Pushy's runtime dependencies on your classpath. They are:

- [netty 4.1.53](http://netty.io/)
- [gson 2.6](https://github.com/google/gson)
Expand Down Expand Up @@ -244,4 +244,4 @@ Callers may also provide a [`MockApnsServerListener`](https://pushy-apns.org/api

Pushy is available under the [MIT License](https://github.com/jchambers/pushy/blob/master/LICENSE.md).

The current version of Pushy is 0.14.1. It's fully functional and widely used in production environments, but the public API may change significantly before a 1.0 release.
The current version of Pushy is 0.14.2. It's fully functional and widely used in production environments, but the public API may change significantly before a 1.0 release.

0 comments on commit c16260a

Please sign in to comment.