Maven Resolver 2.0.15

[cstamas]

Update from 2.0.14

Release notes:
https://github.com/apache/maven-resolver/releases/tag/maven-resolver-2.0.15

EDIT: testing with 2.0.16-SNAPSHOT now that contains a single commit, fix for JDK transport Content-Length header.

[cstamas]

Something is off here, ITs consistently report these errors:

[INFO] 
Error:  Failures: 
Error:    MavenITmng4235HttpAuthDeploymentChecksumsTest.testit:154->AbstractMavenIntegrationTestCase.fail:148 deployedResource DeployedResource{httpMethod='PUT', requestUri='/repo/org/apache/maven/its/mng4235/test/0.1/test-0.1.jar', contentLength='null', transferEncoding='chunked'} use chunked transfert encoding some http server doesn't support that
Error:    MavenITmng4470AuthenticatedDeploymentToProxyTest.testitRelease:179->testit:210->AbstractMavenIntegrationTestCase.fail:148 deployedResource DeployedResource{httpMethod='PUT', requestUri='/repo/org/apache/maven/its/mng4470/release/1.0/release-1.0.jar', contentLength='null', transferEncoding='chunked'} use chunked transfert encoding some http server doesn't support that
Error:    MavenITmng4470AuthenticatedDeploymentToProxyTest.testitSnapshot:189->testit:210->AbstractMavenIntegrationTestCase.fail:148 deployedResource DeployedResource{httpMethod='PUT', requestUri='/repo/org/apache/maven/its/mng4470/snapshot/1.0-SNAPSHOT/snapshot-1.0-20260216.224343-1.jar', contentLength='null', transferEncoding='chunked'} use chunked transfert encoding some http server doesn't support that
[INFO] 
Error:  Tests run: 1028, Failures: 3, Errors: 0, Skipped: 45

What is IMO OFF, is that these are old ITs 4235, 4470... and these same tests should run with Maven 3 as well, but there they pass? Resolver has same changes in http/apache transport....

This needs to be looked into.

[cstamas]

So far investigation points at apache/maven-resolver#1755
Original JDK used temp file with file body publisher (which was an ugly circumvention), the PR new code uses stream body publisher, and seems latter does not pass on payload size to client, hence client (on PUT) does not send content-length anymore.

[cstamas]

Fix apache/maven-resolver#1798
So now question remains: do we punt 2.0.15? And do 2.0.16?

[Bukama]

Fix apache/maven-resolver#1798 So now question remains: do we punt 2.0.15? And do 2.0.16?

I'm fine to directly update to 16