wilx opened a new pull request, #1339:
URL: https://github.com/apache/maven-assembly-plugin/pull/1339
Fixes #1158.
## Summary
Replace the deprecated `MavenProject.getDependencyArtifacts()` lookup used by
module-set dependency resolution with Maven Resolver.
This prevents a `NullPointerException` for reactor modules where Maven does
not
populate the legacy dependency-artifact collection, including `pom`-packaging
projects. It also preserves the intended `useTransitiveDependencies`
behavior:
direct reactor dependencies are included when the option is disabled, while
their transitive dependencies are omitted.
## Implementation
- Resolve module dependencies from the project's dependency graph through
Maven Resolver.
- Select only depth-one dependency nodes for non-transitive module sets.
- Account for the dependency-node parent-list shapes used by Maven Resolver
1.x and 2.x.
- Add unit coverage for missing legacy dependency artifacts and direct
dependency selection.
- Add an Invoker reproducer with a multi-module reactor containing a
`pom`-packaging module, and verify the exact archive contents.
## Compatibility and verification
- Maven 3.9.16: `mvn -Prun-its clean verify` passed (269 unit tests and 151
Invoker builds).
- Maven 4.0.0-rc-5: `mvn clean verify` passed (269 unit tests).
- The processed regression project was also run directly with Maven
4.0.0-rc-5
and Maven 3.6.3; both produced the expected direct-dependency-only archive.
The Maven 4 outer Invoker run is currently affected by Maven Invoker 3.10.1
passing `-D maven.repo.local=...` as two arguments, which Maven 4 rejects.
This
is independent of the plugin change; the same processed integration-test
project passes when Maven receives the correctly formed
`-Dmaven.repo.local=...` argument.
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Your pull request should address just one issue, without pulling in
other changes.
- [x] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
Note that commits might be squashed by a maintainer on merge.
- [x] Write unit tests that match behavioral changes, where the tests fail
if the changes to the runtime are not applied.
This may not always be possible but is a best-practice.
- [x] Run `mvn verify` to make sure basic checks pass.
A more thorough check will be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its
verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
