Skip to content

Conversation

@olamy
Copy link
Member

@olamy olamy commented May 27, 2025

  • test build with jdk23
  • fix ghas
  • some javadoc jdk 23 fixes
  • add jdk23 specific test

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Your pull request should address just one issue, without pulling in other changes.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body.
    Note that commits might be squashed by a maintainer on merge.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
    This may not always be possible but is a best-practice.
  • Run mvn verify to make sure basic checks pass.
    A more thorough check will be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

olamy added 7 commits May 26, 2025 21:56
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
…xing segfault Signed-off-by: Olivier Lamy <olamy@apache.org>
@olamy olamy requested a review from slawekjaranowski May 28, 2025 06:54
@olamy olamy merged commit 26ddc2f into apache:master May 28, 2025
100 checks passed
@olamy olamy deleted the fix-jdk-23-build branch May 28, 2025 07:17
@github-actions github-actions bot added this to the 3.11.3 milestone May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2 participants