slachiewicz commented on issue #2256: URL: https://github.com/apache/maven-resolver/issues/2256#issuecomment-6581461895
A correction to the description: a prefixes file *can* list a file at the repository root. Nexus-generated files do, for example `/archetype-catalog.xml` and its checksums in the file `PrefixesRemoteRepositoryFilterSourceVerifyDeniedTest` uses. Central's `.meta/prefixes.txt` has 24,337 entries, 1,070 of them at the root, but no `/archetype-catalog.xml`, while Central serves that file. So the warning is accurate: Central's file is incomplete for that path. That leaves two places to fix it: 1. Central's prefixes file adds `/archetype-catalog.xml` (and its checksums), so Resolver's check stays as it is. 2. Resolver treats paths at the repository root as outside the filter, since they belong to no group: accept them before the prefix lookup, without verification. This also bypasses a user-provided prefixes file for those paths. I have a five-line change with a test for this, if you prefer it. Which do you want? -- 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]
