slachiewicz opened a new issue, #2251: URL: https://github.com/apache/maven-resolver/issues/2251
Resolver 2.x, as shipped in Maven 3.10.0 and Maven 4, records the source of a downloaded artifact in `_remote.repositories` as `<id>-<sha1(url)>`, for example `central-8fac3ebd6edbaca3c794783fa38088af0aa128e7` (#2080, #2104). Resolver 1.9.x, and so Maven 3.9.x, looks only for the bare repository id. With a local repository shared between Maven 3.9 and Maven 3.10 or 4, Maven 3.9 treats every artifact that the newer Maven downloaded as cached from an unknown repository. It logs "is present in the local repository, but cached from a remote repository ID that is unavailable in current build context" and checks the artifact against the remote repository again. To reproduce, fill an empty local repository with Maven 3.10.0 for a project that depends on `com.fasterxml.jackson.core:jackson-databind:2.20.1`, then build the same project with Maven 3.9.16: it logs the message 42 times. The other direction is quiet, as Resolver 2.x also reads the bare-id entries that 1.9.x writes (#2133). -- 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]
