dnsbtchr opened a new issue, #13385: URL: https://github.com/apache/maven/issues/13385
### Affected version 3.10.0 ### Bug description When using a custom Artifactory/Nexus instance configured as the `central` repository (via profile in settings.xml), Maven 3.10.0 blocks artifact resolution with: `ArtifactFilteredOutException: prefixes: Path <artifact-path> NOT allowed from central` The artifact exists in the repository and is directly accessible via HTTP. The same setup works without issues on Maven 3.9.16. Upgrading from 3.9.16 to 3.10.0 reproduces the issue immediately. Root cause (suspected): The repository serves a prefixes.txt that was generated from the underlying public Maven Central index and therefore does not include internal/private artifact paths. Maven 3.9.x appears to treat prefix filter misses as a soft hint and attempts the download anyway. Maven 3.10.0 treats them as a hard block and skips the request entirely, making internal artifacts that are absent from the prefix list unresolvable. Steps to reproduce: 1. Configure a Artifactory/Nexus virtual repository as central in settings.xml via an active profile 2. The virtual repository aggregates both a public Maven Central proxy and internal local repositories 3. The prefix file served by the virtual repo is generated from the public proxy and does not include paths from the internal local repos 4. Run any build with Maven 3.10.0 that depends on an artifact only present in the internal local repo 5. Resolution fails with`Suppressed: org.eclipse.aether.transfer.ArtifactFilteredOutException: prefixes: Path <artifact-path> NOT allowed from central` -- 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]
