Open stefan-kolb opened 5 years ago
Method too large error: if I understand this correct from the badass jlink docs, all non modular jars are merged together in a single module and thus require no entry in the java list of modules that is this method, that is throwing the method too large error.
The badass-jlink plugin takes a more pragmatic approach by combining all non-modular dependencies into a single jar. This way, only the resulting merged module needs a module descriptor.
Method too large error:
I was in the jlink code - I think, we need to work on that method. I think, we want to learn how to generate bytecode, don't we?
Handbook: https://asm.ow2.io/asm4-guide.pdf
We would need to generate smaller methods and add references to these smaller methods then to the main module descriptor method
Method too large was fixed by us and is now integrated in JDK 21.0.1 as well https://www.oracle.com/java/technologies/javase/21-0-1-relnotes.html
From #3421
TextAreaSkin
andTextFieldSkin
Morerover, the following needs to be fixed at some point but we cannot do much at the moment:
add-opens
andadd-exports
usingmoduleOptions
(precondition: new version of gradle-modules-plugin is released (> 1.5.0))javax.xml.bind
tojakarta.xml.bind
(see #7161) as soon as pdfbox/xmbox is fixed --> https://issues.apache.org/jira/browse/PDFBOX-5061, which is fixed now in PDFBox 3.0JDK-8246197: jlink with many modules failduplicate of JDK-8240567[ERROR] Error: jdk.internal.org.objectweb.asm.MethodTooLargeException: Method too large