slachiewicz opened a new pull request, #13791: URL: https://github.com/apache/maven/pull/13791
Fixes #13786. When a remote repository filter rejects an artifact, the hint blamed repository managers and suggested disabling filtering. The most common way to hit it in a multi-module build, though, is `-pl app` without `-am` when `app` depends on a project of the same build that was not built or installed: the filter is right to reject it. The hint now names the rejected artifact and offers that case first: ``` This error indicates that a remote repository filter has rejected this artifact. If demo:lib:1.0-SNAPSHOT is a project of this build, build it as well, for example with -am, or install it first. Otherwise, this commonly happens with repository managers using virtual/group repositories that do not properly aggregate prefix files. ``` `DefaultExceptionHandler` only sees the exception chain, not the session, so it cannot tell whether the artifact really is a project of the build; this keeps the change to the wording rather than threading the session through. Verified: with the 4.1.0-SNAPSHOT distribution built from this branch, a parent with `lib` and `app` (depending on `lib`), `mvn compile -pl app` → the message above. `DefaultExceptionHandlerTest` checks the new line; `impl/maven-core` → 818 tests pass; spotless clean. -- 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]
