Explain migration of Java 9+ module dependencies

pull/81/head
Richard Körber 2019-03-16 17:51:41 +01:00
parent 197cdb6697
commit 5863eac821
No known key found for this signature in database
GPG Key ID: AAB9FD19C78AA3E0
1 changed files with 2 additions and 0 deletions

View File

@ -4,6 +4,8 @@ This document will help you migrate your code to the latest _acme4j_ version.
## Migration to Version 2.7
- Note that _acme4j_ has an `Automatic-Module-Name` set in the acme-client and acme-utils modules now. If you have added _acme4j_ to your Java 9+ module dependencies, you'll need to fix your dependency declaration to `org.shredzone.acme4j` (acme-client) and `org.shredzone.acme4j.utils` (acme-utils).
- There are no breaking API changes in this version, except of the removal of `CertificateUtils.createTlsAlpn01Certificate(KeyPair, String, byte[])` which has been marked as deprecated in v2.6.
- The ACME draft has been finalized and is now called [RFC 8555](https://tools.ietf.org/html/rfc8555). For this reason, the _acme4j_ API is now stable. There won't be breaking changes to the public API in the future, unless absolutely necessary.