slachiewicz opened a new issue, #13786: URL: https://github.com/apache/maven/issues/13786
### Affected version 4.0.0-rc-7 ### Bug description In a build with a parent, `lib` and `app` (which depends on `lib`), `mvn compile -pl app` without `-am`, with `lib` never installed, fails as expected because `demo:lib:jar:1.0-SNAPSHOT` cannot be found. The message on 4.0.0-rc-7 continues: ``` [ERROR] This error indicates that a remote repository filter has rejected this artifact. This commonly happens with repository managers using virtual/group repositories that do not properly aggregate prefix files. [ERROR] To disable remote repository filtering, add one or both of these to your command line or to .mvn/maven.config: ``` The filter is right to reject the path: `demo:lib` is a subproject of the same build and was never deployed anywhere. The hint sends the user to their repository manager and suggests disabling filtering, when the fix is `-am` or installing `lib` first. 3.9.16 reports only "Could not find artifact demo:lib:jar:1.0-SNAPSHOT", and 3.10.0 the `prefixes: … NOT allowed from central` line without the hint. Expected: when the rejected artifact is one of the projects of the current build (the reactor), say so and suggest `-am` (or `-pl` with that project), instead of the repository-manager hint from `DefaultExceptionHandler`. -- 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]
