slachiewicz opened a new pull request, #2119: URL: https://github.com/apache/maven-resolver/pull/2119
Brings the 1.9.x line level with `master` on five changes it never received. | Change | What `master` has that 1.9.x does not | | --- | --- | | Checksum reads and logged values | `LogSanitizer`, absent on 1.9.x, and an upper bound on checksum file reads in `ChecksumUtils` | | Header scoping across redirects | `OriginScopedHeadersInterceptor` and `ResolverRedirectStrategy`, neither present on 1.9.x | | Checksum policy merge | The policy strength comparator and mirror clamping in `DefaultRemoteRepositoryManager` | | Descriptor cache key | `DataPool.toKey` keying on `(artifact, repositories)`; 1.9.x keys on the artifact alone, so a descriptor read from one repository can be handed back for a request naming another | | Not-found markers | Expiry of stale markers once an artifact is downloaded | The transport module differs between the lines: `master` renamed it to `maven-resolver-transport-apache`, so the header-scoping change is applied against 1.9.x's `maven-resolver-transport-http` rather than lifted. Two further changes from the same batch are deliberately not here, because `master` does not carry them either and a maintenance line should not lead: bounding RFC 9457 error-body reads, and requiring verification before relabeling a resolved artifact. Both want a `master` PR first. Verified: `mvn clean install` -> BUILD SUCCESS, 1078 tests, 0 failures, 0 errors; `spotless:check` clean across all 18 modules. *This change was created with AI assistance.* -- 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]
