slachiewicz opened a new pull request, #2160: URL: https://github.com/apache/maven-resolver/pull/2160
Fixes #2159 ### Description In #2135, `EnhancedLocalRepositoryManagerFactory.DEFAULT_LEGACY_LOCAL_REPOSITORY` was introduced with default `true`. Under this default, `applyTracking` accepts locally cached artifacts across different repository URLs if they share the same repository ID (prefix matching `repoIdPrefix = getKey(path, legacyKey + "-")`). This PR defaults `DEFAULT_LEGACY_LOCAL_REPOSITORY` to `false` in Resolver 2 to preserve strict URL-qualified provenance tracking by default, avoiding unexpected cross-URL cache acceptance when repository IDs collide. Users sharing a local repository with Maven 3.9 / Resolver 1.x can explicitly configure `aether.enhancedLocalRepository.legacyLocalRepository=true` to re-enable legacy behavior. - [x] Your pull request should address just one issue, without pulling in other changes. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. - [ ] Run `mvn verify` to make sure basic checks pass. - [ ] You have run the integration tests successfully (`mvn -Prun-its verify`). - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) -- 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]
