efegokdemir opened a new pull request, #13386: URL: https://github.com/apache/maven/pull/13386
## What changed Maven now enables Resolver's `aether.remoteRepositoryFilter.prefixes.verifyDeniedDropsTree` behaviour by default. When Resolver verifies that a path denied by an auto-discovered prefix file exists, it can discard that incomplete prefix tree and continue resolving the artifact. Explicit user settings still override the default. ## Why A virtual repository can expose a `.meta/prefixes.txt` file that does not include artifacts available through its other members. Maven 3.10.0 then rejects those artifacts even after confirming that the denied POM exists. ## Testing - Reproduced with a local HTTP repository: Maven 3.10.0 fails without the property and succeeds when it is enabled. - The new default-setting test failed before the implementation (`expected true, got null`) and passes after it; a second test verifies an explicit `false` override is preserved. - `mvn -pl maven-core -am verify` passed (Maven Core: 404 tests, 1 skipped; all 11 reactor modules successful). - Core IT was not run. ## Checklist - [x] This pull request addresses one issue. - [x] The description explains what changed, how, and why. - [x] The commit has a meaningful subject line. - [x] Unit tests cover the behaviour change. - [x] Ran the targeted verify command: `mvn -pl maven-core -am verify`. - [ ] Ran the Core IT. - [x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004. Fixes #13385 -- 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]
