Skip to content

Conversation

slawekjaranowski
Copy link
Member

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 Core IT successfully.

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.

def buildOs = 'linux'
def buildJdk = '8'
def buildMvn = '3.9.9'
def buildMvn = '3.x.x'
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@slawekjaranowski slawekjaranowski added maintenance build Pull requests that change the build process and removed maintenance labels Jun 8, 2025
@slawekjaranowski slawekjaranowski added this to the 3.9.11 milestone Jun 8, 2025
@slawekjaranowski slawekjaranowski merged commit 9ac9bc2 into maven-3.9.x Jun 8, 2025
36 checks passed
@slawekjaranowski slawekjaranowski deleted the build-3.x-mvn-3.9.10 branch June 8, 2025 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Pull requests that change the build process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants