Google GitGoogle Git
Sign in
apache/maven-install-plugin/refs/heads/fix/MINSTALL-205-install-file-parallel-warning
commit
dad361c172e64666f1d6eb0e660a429a76649e0a
[log]
author
Guillaume Nodet <gnodet@gmail.com>
Wed Sep 23 21:43:00 2026 +0000
committer
Guillaume Nodet <gnodet@gmail.com>
Wed Sep 23 21:43:00 2026 +0000
tree
4c799d44ab531d6dbb3fd77b06e3f44d6190288a
parent
a3c7c70ef55d9432e7f89323a11c5cf28e681474 [diff]
[MINSTALL-205] Remove unnecessary aggregator=true from install-file

install-file does not access the reactor projects - it installs an
arbitrary external file into the local repository. The aggregator=true
flag was causing Maven to acquire an exclusive write lock when the mojo
ran, serializing all concurrent install-file executions in parallel
builds (-T N) and emitting a spurious warning:

  The org.apache.maven.plugins:maven-install-plugin:...:install-file
  aggregator mojo is already being executed in this parallel build,
  those kind of mojos require exclusive access to reactor to prevent
  race conditions. This mojo execution will be blocked until the
  aggregator mojo is done.

The mojo already carries projectRequired=false which is sufficient to
allow invocation from a multi-module root without a project context.
Removing aggregator=true lets concurrent install-file executions run
truly in parallel without any warning.

Fixes: https://github.com/apache/maven-install-plugin/issues/251
9 files changed
tree: 4c799d44ab531d6dbb3fd77b06e3f44d6190288a
  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 Install 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.

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