slachiewicz opened a new pull request, #2252: URL: https://github.com/apache/maven-resolver/pull/2252
`EnhancedLocalRepositoryManager` now also accepts the key that Resolver 2.x writes by default, `<id>-<sha1(url)>`, when the id and URL match the request repository; for a repository manager the request context is part of the hash, as in Resolver 2's `nidAndHurlRepositoryKey`. Entries are still written with the bare id, so other 1.9.x builds keep reading them. Unlike #2125, this changes only the read side. Fixes #2251. Verified: Maven 3.9.16 with this `maven-resolver-impl` on a local repository filled by Maven 3.10.0 → no "cached from a remote repository ID that is unavailable" messages (stock 3.9.16: 42). Two of the three new tests fail without the change. - [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. - [x] Run `mvn verify` to make sure basic checks pass. - [ ] You have run the integration tests successfully (`mvn -Prun-its verify`). - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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]
