gnodet opened a new pull request, #12341:
URL: https://github.com/apache/maven/pull/12341
Backport of #12338 to `maven-4.0.x`.
Cherry-pick of ffd7baa041 — conflict resolved in the IT test.
## Summary
- Remove `maven-resolver-transport-jdk` from the distribution, making Apache
HttpClient the only bundled HTTP transport
- The JDK HTTP transport (backed by methanol) has proven flaky on Windows CI
with race conditions in the gzip/inflater code path (`NullPointerException:
Inflater has been closed`)
## Changes
- `apache-maven/pom.xml`: removed `maven-resolver-transport-jdk` dependency
from the distribution
- `impl/maven-cli/pom.xml`: switched `mvnup` dependency from `transport-jdk`
to `transport-apache`
- `AbstractUpgradeStrategy` (mvnup): switched DI provider from
`JdkTransporterFactory` to `ApacheTransporterFactory`
- `MavenITmng7470ResolverTransportTest`: default transport test now expects
`ApacheTransporter`; removed `testResolverTransportJdk` test; simplified
version-detection helpers (kept backward compat for old `HttpTransporter` class
name)
## Conflict resolution
The IT test on `maven-4.0.x` has a version-range constructor
`super("[3.9.0,)")` and backward-compat logic for the old `HttpTransporter`
class name (pre-4.0.0-alpha-9). These were preserved. JDK-specific helpers
(`isJdkTransportUsable`, `isJdkTransportPresent`) were replaced with a single
`isApacheTransportRenamed()` method.
--
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]
