Hi Jan, Am Mittwoch, den 07.04.2021, 19:57 +0200 schrieb Jan Lahoda: > > > > > thank you, but this is known. I also note, that in most cases this > is > > just a stawman argument. The last bug I fixed in that area was also > put > > of as "you run from classpath, so you are on your own". > > > > It turned out, that the bug was caused by wrong assumptions and > > manifested whenever the classes were not loaded from the system > class > > loader, which is just much more common in the class loader world, > than > > in JPMS world. Setting up a module layer and loading JavaFX there > > breaks it equally. > > > > I don't think I have much on the problem as such (at least not yet), > but > wanted to say that if (at some point) it would help to run Open JFX > (or > something else) in module layers, we could try that. I hope it should > be > doable. But if I understand you properly, it sounds OpenJFX does not > work > well even when deployed as modules (into layers), which sounds like > something for OpenJFX to solve.
yes - fiddeling with ModuleLayers made me realize, that the modular world, is not that bad and indeed it should be possible to integrate it into the netbeans module system. I'm aware of your prototype, but as of yet failed to make time to really look into it. This whole thread was not so much intendend to find the problem (which indeed is rooted in OpenJFX), but to find a work-around. For my personal interest, I have 13 crashing because data-URIs are used and for the NetBeans project 16 breaks wizards. At this point - either a prerelease of 17 is build in time for netbeans release with the fix currently under review and we bump to that - we rollback to 13 (which makes me sad) - find a different work around, that does not break the module system I kind of hoped, that there is some option in the NetBeans module system to mess with the systemclass loader. Greetings Matthias
