Google GitGoogle Git
Sign in
apache/maven-compiler-plugin/refs/heads/master
commit
734b166371399594c4666385f7e490e5211bdd2e
[log]
author
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Wed Sep 23 19:25:51 2026 +0200
committer
GitHub <noreply@github.com>
Wed Sep 23 19:25:51 2026 +0200
tree
7643b3e016cbd26770dd24c35d66907523f4b281
parent
b87a280acc3bc5ff1ddd3cefbfab918bb99c27f7 [diff]
Bump org.apache.maven.plugins:maven-plugins from 49 to 50 (#1132)

* Bump org.apache.maven.plugins:maven-plugins from 49 to 50

Bumps [org.apache.maven.plugins:maven-plugins](https://github.com/apache/maven-parent) from 49 to 50.
- [Release notes](https://github.com/apache/maven-parent/releases)
- [Commits](https://github.com/apache/maven-parent/commits)

---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-plugins
  dependency-version: '50'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Fix IT pom.xml files after maven-plugins 50 upgrade

The maven-plugins parent 50 renamed the property
version.maven-surefire to version.maven-surefire-plugin.
Update the multirelease-patterns ITs to use the new name.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Guillaume Nodet <gnodet@gmail.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
8 files changed
tree: 7643b3e016cbd26770dd24c35d66907523f4b281
  1. .github/
  2. src/
  3. .asf.yaml
  4. .git-blame-ignore-revs
  5. .gitignore
  6. AGENTS.md
  7. Jenkinsfile.disable
  8. LICENSE
  9. NOTICE
  10. pom.xml
  11. README.md
  12. SECURITY.md
README.md

Contributing to Apache Maven Compiler Plugin

Apache License, Version 2.0, January 2004 Maven Central Maven Central Reproducible Builds

You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

Getting Started

  • Make sure you have a GitHub account.
  • If you‘re planning to implement a new feature, it makes sense to discuss your changes on the dev list first. This way you can make sure you’re not wasting your time on something that isn‘t considered to be in Apache Maven’s scope.
  • Submit a ticket for your issue, assuming one does not already exist.
    • Clearly describe the issue, including steps to reproduce when it is a bug.
    • Make sure you fill in the earliest version that you know has the issue.
  • Fork the repository on GitHub.

Build requirements

Building requires Maven 4. Executing the tests on Windows requires the developer mode. This is enabled with Settings > Update & Security > For Developers.

Making and Submitting Changes

We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us:

  • Create a topic branch from where you want to base your work (this is usually the master branch). Push your changes to a topic branch in your fork of the repository.
  • Make commits of logical units.
  • Respect the original code style: by using the same codestyle, patches should only highlight the actual difference, not being disturbed by any formatting issues:
    • Only use spaces for indentation.
    • Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted, create a separate PR for this change.
    • Check for unnecessary whitespace with git diff --check before committing.
  • Make sure you have added the necessary tests (JUnit/IT) for your changes.
  • Run all the tests with mvn -Prun-its verify to assure nothing else was accidentally broken.
  • Submit a pull request to the repository in the Apache organization.

If you plan to contribute on a regular basis, please consider filing a contributor license agreement.

Additional Resources