Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate Indy to JDK11. #1505

Open
whitingjr opened this issue Feb 5, 2020 · 5 comments
Open

Migrate Indy to JDK11. #1505

whitingjr opened this issue Feb 5, 2020 · 5 comments

Comments

@whitingjr
Copy link
Contributor

To make the transition to JDK11 there are changes necessary to the codebase.

These can be summarised as:

  • Add module descriptor metadata
  • Swap out API removed from the JRE

See the JDK11 Release Notes for details.
@whitingjr
Copy link
Contributor Author

Swapping out the classes has been done in PR #1517

@whitingjr
Copy link
Contributor Author

To test with JDK11 a system property needs adding. Without the property the BMUnit tests error. This will be added by the PR #1547

@whitingjr whitingjr changed the title Add Java 9 Module information to Indy projects. Migrate Indy to JDK11. Mar 17, 2020
@whitingjr
Copy link
Contributor Author

There is an open issue JDK-8228343 with the tooling that comes with OpenJDK11 when running in a container. Due to pid id lookups in the wrong namespace.

@whitingjr
Copy link
Contributor Author

Function Tests also are broken. Details in #1621

@whitingjr whitingjr mentioned this issue Sep 18, 2020
Merged
@whitingjr
Copy link
Contributor Author

At runtime JDK11 is being used. This issue will remain open until the container image uses JDK8 compiled byte-code.

@whitingjr whitingjr mentioned this issue Jan 22, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@whitingjr