Skip to content

Conversation

@martins-avots
Copy link
Contributor

@martins-avots martins-avots commented Nov 23, 2025

Start working on #1521 by updating one resource usage.
All test worked locally.
This is a test pull-request, in order to check how PRs are done.
Additional fixes will be done in later on with an additional PR.

Where do I send the signed Individual Contributor License Agreement ?

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.

@cstamas cstamas changed the title Use try-with for resource (#1521) Use try-with for resource in test HttpServer (#1521) Nov 27, 2025
@cstamas
Copy link
Member

cstamas commented Nov 27, 2025

From ICLA PDF: Please complete and sign this Agreement, and then email a pdf copy to [email protected] only (do not copy any other persons or lists).

@cstamas cstamas merged commit 96a7195 into apache:master Nov 27, 2025
14 checks passed
@github-actions
Copy link

@cstamas Please assign appropriate label to PR according to the type of change.

@github-actions github-actions bot added this to the 2.0.14 milestone Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants