Google GitGoogle Git
Sign in
apache/maven-filtering/e5c376533409a75598b4022f4245d4e66dcafe4d
commit
e5c376533409a75598b4022f4245d4e66dcafe4d
[log]
author
Guillaume Nodet <gnodet@gmail.com>
Sat Sep 26 19:12:10 2026 +0200
committer
GitHub <noreply@github.com>
Sat Sep 26 19:12:10 2026 +0200
tree
da5226f1e083c666262b98c41b0ca8a49d6b9d87
parent
27a541e0b5518f4b19eddeb14cc4d103d66697a3 [diff]
feat: introduce ChangeDetection strategy for file copy (MRESOURCES-453)

- Add ChangeDetection enum with 5 strategies: TIMESTAMP, CONTENT (default), TIMESTAMP_AND_CONTENT, ALWAYS, NEVER
- New changeDetection field on AbstractMavenFilteringRequest and Resource (per-resource override takes precedence)
- New FilteringUtils.copyFile(…, ChangeDetection) overload returning boolean (true=written, false=skipped); old boolean overwrite signature deprecated
- New MavenFileFilter.copyFileWithResult(…, ChangeDetection) method
- DefaultMavenResourcesFiltering logs "Copying file X" or "Skipping file X (up to date)" based on actual copy outcome
- MavenResourcesExecution.isOverwrite()/setOverwrite() deprecated, now delegate through ChangeDetection
- Port of maven-filtering-3.x commit d9bc10a to master (Path-based API)
- Fixes apache/maven-resources-plugin#453, #286, #316
8 files changed
tree: da5226f1e083c666262b98c41b0ca8a49d6b9d87
  1. .github/
  2. src/
  3. .asf.yaml
  4. .git-blame-ignore-revs
  5. .gitignore
  6. deploySite.sh
  7. Jenkinsfile
  8. LICENSE
  9. NOTICE
  10. pom.xml
  11. README.md
README.md

Contributing to Apache Maven Filtering

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

Maven 3: maven-filtering-3.x 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.

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

Additional Resources