Remove dns-java workarounds

[adutra]

The latest 3.6.2 version seems to fix the issue. I also tested with Postgres using the docker-compose files from #859 and had no issues.

[adutra]

Relates to #583

[snazy]

FYI the latest dnsjava versions come with META-INF/services/java.net.spi.InetAddressResolverProvider referencing their custom DNS resolver. But IIRC, that needs to be explicitly enabled via a system property.

[adutra]

FYI the latest dnsjava versions come with META-INF/services/java.net.spi.InetAddressResolverProvider referencing their custom DNS resolver. But IIRC, that needs to be explicitly enabled via a system property.

Indeed, that SPI impl was introduced in 3.6.0 and is enabled by a system property: org.dnsjava.spi.enable. I do not fully understand why the problem occurred, and why it disappeared. Maybe related to the switch to Quarkus and/or the fact that we don't produce shaded artifacts anymore.

[snazy]

projectnessie/nessie#9951 and projectnessie/nessie#9943 have some context. I think there was a problem with how dnsjava.jar was built (mr-jar) - and the Java runtime version - and likely, as you said, whether it's then run in an uber-jar.

[dimas-b]

@adutra : IIRC, dnsjava used to break EclipseLink with PostgreSQL. Did you have a change to test that? If bootstrap with PostgreSQL works, that's a good enough test.

Update: for extra certainty I think we ought to test on local machines :)

[dimas-b]

Java version may also be a factor.

[adutra]

@adutra : IIRC, dnsjava used to break EclipseLink with PostgreSQL. Did you have a change to test that? If bootstrap with PostgreSQL works, that's a good enough test.

Update: for extra certainty I think we ought to test on local machines :)

I tested with the new docker-compose files from #859 which include an example with EclispeLink and Postgres. Do you think that's enough?

Java version may also be a factor.

I only tested with Java 21.

[snazy]

I only tested with Java 21.

I guess that's fine then. The runtime requires Java 21.

[dimas-b]

LGTM 👍 Thanks for tracking this down @adutra ! I guess we can always fix this again if it does not work in some env. :)