slachiewicz opened a new pull request, #939: URL: https://github.com/apache/maven-wagon/pull/939
The HTTP TCK moved to JUnit 5 in #937, and the developer guide still describes the JUnit 4 shape: it calls the suite JUnit 4 and shows `@RunWith(Suite.class)` with `@Suite.SuiteClasses`. The guide now matches `wagon-http`'s actual `TckTest`, and names `junit-platform-suite` as a dependency a provider has to add — without it the suite class compiles but selects nothing, which is a quiet way to end up testing zero cases. This also removes `wagon-tcks/wagon-tck-http/sample-tck-consumer`. It is not a reactor module and nothing references it, so it has never been built or compiled against; it pins `wagon-http-lightweight` 1.0-beta-6 and `wagon-tck-http` 1.0-beta-7-SNAPSHOT, and its `TestSuite` is still `@RunWith(Suite.class)`. As the one worked example of consuming the TCK it now shows the wiring the guide warns against, so a decade-stale sample is worse than none. The guide's own "Wiring the TCK into a provider" section covers what it used to demonstrate. *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]
