[jira] [Comment Edited] (MRESOLVER-417) Create HTTP test suite a la "TCK"

["Tamas Cservenak (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRESOLVER-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777469#comment-17777469 ] 

Tamas Cservenak edited comment on MRESOLVER-417 at 10/19/23 9:04 PM:
---------------------------------------------------------------------

The Jetty-9 module is to be removed as I commented yesterday in Slack.
The jdk-8 module runs on Java8, so no java.net.http.HttpClient available, hence throws "No transport", but take a peek at priority, so in reality it never executes (unless no other HTTP transport existing on classpath). Out of jdk-8 (no-transport) and jdk-11 (does the job) is created the jdk (multi release JAR).

The jdk module creation may look complicated at first sight, but this was the only way to produce "jdk" multi-release jar (assembled from jdk-8 + jdk11), but also preserve enforcer, spotless, and make it usable in IDE as well.


was (Author: cstamas):
The Jetty-9 module is to be removed as I commented yesterday in Slack.
The jdk-8 module runs on Java8, so no java.net.http.HttpClient available, hence throws "No transport", but take a peek at priority, so in reality it never executes (unless no other HTTP transport existing on classpath). Out of jdk-8 (no-transport) and jdk-11 (does the job) is created the jdk (multi release JAR).

> Create HTTP test suite a la "TCK"
> ---------------------------------
>
>                 Key: MRESOLVER-417
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-417
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Now that we have 3 (4 w/ Wagon) HTTP capable resolver transports, we need some common reusable across HTTP Transports test suite, probably w/ "tunable" features.
> Requirements aside of "most basic functionality":
> * MRESOLVER-396 Back off
> * MRESOLVER-393 Retain last modified (on files)
> * MRESOLVER-382 Setting outgoing interface
> * MRESOLVER-361 Unreliable TCP and retries
> * MRESOLVER-347 and MRESOLVER-348 Pool controls, reuse connection, max TTL
> * MRESOLVER-339 and MRESOLVER-315 Preemptive auth
> * MRESOLVER-341 Preemptive PUT auth
> * MRESOLVER-328 SSL insecure mode
> * MRESOLVER-326 Retries on certain errors
> The test should use _standard Resolver configuration with different transports_ as described on page https://maven.apache.org/resolver/configuration.html
> Hence, testing of Wagon is out of scope, as it uses totally different, ancient Plexus-XML based configuration, does not obey standard resolver configuration properties.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)