The problem is the stone-aged bnd library that is used, which cannot deal with Java 11 classes/jars. The following patch creates a proper manifest just fine. I'm not sure if the ivy.xml changes are really needed or if there are other places that need fixing - the complexity of the build system is beyond my comprehension. diff -u build/build.xml ../Projects/hsqldb/hsqldb-svn-r6348/base/trunk/build/build.xml --- build/build.xml 2021-05-14 23:51:15.000000000 +0200 +++ ../Projects/hsqldb/hsqldb-svn-r6348/base/trunk/build/build.xml...
Ahm, no, why should this not work? I would obviously not use both module systems at runtime, but there's no reason to not include OSGi metadata at the same time as Java Module information. From the release notes my understanding was that 2.6.0 adds the module information and is thus compiled against Java 11.
Release 2.6.0 is missing OSGi metadata
Type conversion error in version 2.1.7, in org.xbill.DNS.SetResponse.getNS(SetResponse.java:184)
If you still think this is an issue/use case, please create a pull request on dnsjava's new home at Github: https://github.com/dnsjava/dnsjava
License update in README
Done on Github
Cant get records for ANY