Switch back to java 17 build#1410
Conversation
| <maven.javadoc.plugin.version>3.12.0</maven.javadoc.plugin.version> | ||
| <maven.source.plugin.version>3.4.0</maven.source.plugin.version> | ||
| <maven.checkstyle.plugin.version>3.6.0</maven.checkstyle.plugin.version> | ||
| <maven.checkstyle.plugin.version>3.1.2</maven.checkstyle.plugin.version> |
There was a problem hiding this comment.
do we really need to do a downgrade on this?
There was a problem hiding this comment.
Newer versions won't build against Java 17.
KyleAure
left a comment
There was a problem hiding this comment.
Looks good, just a few things that still need to be reverted from this commit: 9f445d2
Namely:
- tck/.../TCKArchiveProcessor.java
- tck/.../DataSignatureTestRunner.java
- tck-dist/.../data-tck-reference-guide.adoc
- spec/.../README.adoc
- README.adoc
Thanks - I updated the readme, but running the TCK on Java 17 is intentionally left out. We will tolerate Java 17, but we aren't requiring or expecting anyone to certify on it. The goal from the issue that was opened is "at least having API/annotations jar be Java 17 compatible letting it be up to implementations to set the bar higher" along with that we also give implementations the benefit of being able to compile a single shared source for Data 1.0 and 1.1 implementations that is built against Java 17. And some implementations might allow users to try out early access versions on Java 17 (I know this has been requested as well). None of these require the TCK to run on Java 17. |
Resolves #1341 to switch us back to building with Java 17 and generating Java 17 compatible API classes for Data 1.1.