Google Git
Sign in
apache / maven-resources-plugin / 1e59b45abd7e9f9a8abe8bdab99c8e0da14ca432
commit1e59b45abd7e9f9a8abe8bdab99c8e0da14ca432[log] [tgz]
authorSlawomir Jaranowski <s.jaranowski@gmail.com>Mon Dec 01 22:08:12 2025 +0100
committerSlawomir Jaranowski <s.jaranowski@gmail.com>Tue Dec 02 20:23:26 2025 +0100
treea8209121f5b9471809c1009b0f08efb76903c5fa
parentb07d56e2b1c400da89d5ed0e6fa4e0466b240457 [diff]
Migration to JUnit 5 - avoid using AbstractMojoTestCase

also:
- refactor PropertyUtilsTest - it is not Mojo test, move use cases from advanced amd enhanced examples

- CopyResourcesMojoTest - test copy-resources instead of resources goal, add more tests for filtered and not filtered resources
14 files changed
tree: a8209121f5b9471809c1009b0f08efb76903c5fa
  1. .github/
  2. src/
  3. .asf.yaml
  4. .git-blame-ignore-revs
  5. .gitignore
  6. deploySite.sh
  7. Jenkinsfile
  8. pom.xml
  9. README.md
README.md

Contributing to Apache Maven Resources Plugin

Apache License, Version 2.0, January 2004 Maven Central Maven Central Reproducible Builds Jenkins Status Jenkins tests

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.

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.
  • Update your JIRA ticket and include a link to the pull request in the ticket.

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

Additional Resources