Cache projectsWithDeployExecution list to avoid O(N²) reactor scan
DeployMojo.allProjectsMarked() calls hasDeployExecution() for every
reactor project on every module invocation. hasDeployExecution() calls
getPluginsAsMap() for each project, producing O(N²) evaluations in a
large reactor build (e.g., 4383² ≈ 19.2M calls in a 4383-module project).
Fix: cache the filtered list of projects with deploy executions in the
first reactor project's plugin context. The list is invariant during a
build. Also simplify allProjectsMarked() to only check the projects
that actually have deploy executions, rather than iterating the full
reactor and testing the disjunction (hasState || !hasDeployExecution).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 file changed
tree: 13cdae66bab399eb5b8d740c7c58ef088155633e
- .github/
- src/
- .asf.yaml
- .git-blame-ignore-revs
- .gitignore
- AGENTS.md
- Jenkinsfile.disable
- LICENSE
- NOTICE
- pom.xml
- README.md
- SECURITY.md
README.md
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
