wilx opened a new pull request, #12831:
URL: https://github.com/apache/maven/pull/12831
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.
- [ ] 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.
- [ ] You have run the [Core IT][core-its] successfully.
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).
## Description
Backport of #12658 from `master` to `maven-4.0.x`.
`ReactorReader` currently returns the reactor project's build POM for every
artifact whose extension is `pom`, without considering its classifier.
Consequently, resolving an attached classified POM from the reactor returns
`pom.xml` instead of the attached artifact.
This change limits the build-POM shortcut to unclassified POM requests.
Classified POMs proceed through the existing artifact matching path, which
selects the attached artifact by extension and classifier. Ordinary reactor POM
and consumer-POM resolution remain unchanged.
The production change is patch-identical to #12658. The Core IT uses the
File/String-based verifier API and suite-order registration required by the
`maven-4.0.x` test harness.
Fixes apache/maven-dependency-plugin#1024
## Tests
- Full root `clean verify`: all 38 modules passed with Maven 3.9.16 and Java
17.
- `spotless:apply`: no formatting changes.
- Focused `MavenITmdep0590ClassifiedPomArtifactFromReactorTest` against the
freshly built Maven `4.0.0-SNAPSHOT` distribution: 1 test, 0 failures, 0
errors, 0 skipped.
[core-its]: https://maven.apache.org/core-its/core-it-suite/
--
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]
