Hi Oleg

Thank you for checking this and sorry about the broken artifacts.

You are right. The artifacts were compiled to Java 1.8 bytecode, but
apparently against a newer JDK API, so the resulting binaries are not
actually Java 8 runtime compatible.

I will double-check my Maven toolchain configuration and rebuild with a
real Java 8 toolchain, then verify the produced artifacts by running the
relevant tests on a Java 8 runtime before publishing anything else.

Since the artifacts are already in Maven Central and cannot be replaced, I
assume the right fix is to cut a corrected follow-up release, most likely
5.5-beta2, unless you prefer a different versioning approach.

Sorry again for the trouble.

Arturo


Arturo


On Sat, Jun 6, 2026 at 11:46 AM Oleg Kalnichevski <[email protected]> wrote:

> Hi Arturo
>
> Thank you making the release happen. Unfortunately I discovered a
> problem with the binary artifacts published to Maven central.
>
> The release artifacts have been correctly built Java 1.8 bytecode
> compatible but they have been built against Java 17 libraries which
> makes them unusable with Java 1.8 runetime.
>
> ```
> [ERROR]   TestURIUtils.testExtractHost:126 » NoSuchMethod
> java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
> [ERROR]   TestURIUtils.testHttpLocationRedirect:204 » NoSuchMethod
> java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
> [ERROR]   TestURIUtils.testHttpLocationWithAbsoluteFragment:192 »
> NoSuchMethod java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
> [ERROR]   TestURIUtils.testHttpLocationWithRedirectFragment:222 »
> NoSuchMethod java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
> [ERROR]   TestURIUtils.testHttpLocationWithRelativeFragment:173 »
> NoSuchMethod java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
> [ERROR]   TestURIUtils.testResolve:49 » NoSuchMethod
> java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
> [ERROR]   TestURIUtils.testResolveOpaque:111 » NoSuchMethod
> java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
> ```
>
> I suspect your Maven toolchain configuration is wrong. It likely uses
> Java 17 JDK to build Java 1.8 artifacts instead of Java 1.8 JDK.
>
> Please double-check your Maven toolchain config.
>
> At the moment I am not able to upgrade HttpClient master to HttpCore
> 5.5-beta1 due to above mentioned problem with ByteBuffer
> incompatibility.
>
> Oleg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to