Skip to content
This repository has been archived by the owner on Feb 23, 2023. It is now read-only.

Introduce preliminary Java 16 compatibility #720

Closed
sdeleuze opened this issue Apr 10, 2021 · 2 comments
Closed

Introduce preliminary Java 16 compatibility #720

sdeleuze opened this issue Apr 10, 2021 · 2 comments
Assignees
@sdeleuze
Labels
type: task A general task
Milestone
0.10.0

Comments

@sdeleuze
Copy link
Contributor

sdeleuze commented Apr 10, 2021 •
edited

  • Update ClassDescriptorTests#resolveStringShouldHaveInterfaces to use stringClass.getInterfaces()).hasSizeGreaterThanOrEqualTo(3)
  • ASM 9.0 should be fine
  • Gradle 7.0 should be needed
  • Test on the CI if possible
@sdeleuze sdeleuze added the type: task A general task label Apr 10, 2021
@sdeleuze sdeleuze added this to the 0.10.0 milestone Apr 10, 2021
@sdeleuze sdeleuze self-assigned this Apr 10, 2021
sdeleuze added a commit that referenced this issue Apr 19, 2021
@sdeleuze
Introduce Java 16 compatibility
85bca6e 
See gh-720
@sdeleuze
Copy link
Contributor Author

Let's test on the CI when Java 8 support will be sunset and Java 17 support available.

@sdeleuze sdeleuze changed the title Introduce Java 16 compatibility Introduce preliminary Java 16 compatibility May 11, 2021
@sdeleuze
Copy link
Contributor Author

Compatibility is done at Spring Native level, but requires some refinements at GraalVM level. As a consequence, Java 16 support is for now best effort, and is not yet introduced
at buildpack level.

Our major focus is on upcoming Java 17 (LTS) support, this is tracked via #773.

@sdeleuze sdeleuze mentioned this issue May 11, 2021
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sdeleuze sdeleuze

Labels
type: task A general task
Milestone
0.10.0
Development

No branches or pull requests
1 participant
@sdeleuze