slachiewicz commented on issue #1954:
URL:
https://github.com/apache/maven-resolver/issues/1954#issuecomment-5495528723
Following discussion and maintainer feedback, we decided to implement the
Apache HttpClient 5.x support as a **new dedicated module
(`maven-resolver-transport-apache5`)** rather than an in-place upgrade of
`maven-resolver-transport-apache`.
### Rationale:
1. **Wagon HTTP Coexistence:** `maven-resolver-transport-apache` (HttpClient
4.5.x) shares client and connection infrastructure with Wagon HTTP. Modifying
it in-place would create classpath conflicts for consumers and plugins that
still rely on Wagon or HttpClient 4.x.
2. **Backward Compatibility & Flexible Adoption:** Keeping both modules
allows existing integrations (such as Maven 3.10.x) to remain on `apache`
(HC4), while newer environments (such as Maven 4.1+) or users explicitly
selecting `-Daether.transport.http.transporter=apache5` can adopt HttpClient
5.x.
3. **Clean Module Boundary:** The new module uses `@Named("apache5")` and
`org.eclipse.aether.transport.apache5` package namespace, avoiding
split-package issues in JPMS/OSGi when both modules are on the runtime
classpath.
PR https://github.com/apache/maven-resolver/pull/2103 has been updated
accordingly.
--
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]
