slachiewicz commented on issue #645: URL: https://github.com/apache/maven-wagon/issues/645#issuecomment-5225727230
Still open. Worth noting that the usual answer to this one — the provider is deprecated and goes away in 4.0.0 — does not currently dispose of it. Wagon 4.0.0 has never been released: `master` is `4.0.0-M1-SNAPSHOT` with no tag, the last release is 3.5.3, and the `wagon-3.x` branch is `3.5.4-SNAPSHOT` and still active. So the deprecation points at a version nobody can run, and the 3.x line is expected to stay for the time being. One thing does limit the blast radius: `wagon-http-lightweight` is not bundled in any Maven distribution. Maven 3.9.16, Maven 4.0.0-SNAPSHOT and Maven 4.1.0-SNAPSHOT all ship only `wagon-provider-api`, `wagon-file`, `wagon-http` and `wagon-http-shared`, all at 3.5.3. So this affects users who add the provider explicitly rather than anyone running a stock Maven. That makes the original proposal — removing the provider rather than fixing the buffering — easier, not harder, but it is a decision for dev@ rather than something to leave implied by a site notice. -- 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]
