Ok, after many tries I figured out something:
- The vtk java build fails runs if you use a modern JVM (21) The dependencies are broken and wont load.
- If you use an old Java for the build (e.g. 9) the build fails at jar-creation when you build debug Dlls. These Dlls are loadable.
- If you build release with old java, the dlls fails again to be loaded into a modern JVM.
So there is no way at the moment to build a vtk 9.4.2. release and load it into an actual JVM.
So there is no migration path for java products based on vtk at the moment.
Is there a ticket for this or anymore knowledge? Could we support somehow? For us this is a real major issue, cause we have several commerical products depending on these wrappings massivly . Migration is necessary, major feature are blocked…