Hi all, and here follows my first try of a contribution.
NETBEANS-3424 is DB related and around a year ago I provided a work around for the problem. The problem was caused by the fact that Derby became repackaged for JPMS modularization and that's why there must be added the derbyshared.jar and derbytools.jar to make it work and as far as I remember Netbeans did not do that out of the box when registering the driver. It was a very long time ago that I was working on it, so please forgive me if I forgot anything or tell you some garbage... I thought proposing a work around in the corresponding bug report or perhaps adding a missing file anywhere to make it work is a small enough amount of work to to start a first contribution with :-) I was a bit confused which parts of the code are used for what. RegisterDerby and DerbyOptions seem to be involved, but it also looks like it is nbbuild related as it seems to ship some of the files together with Netbeans. So when Netbeans is used with Java >= 9 (as NB's runtime ??? or as the project's runtime ??? - can't remember), the missing JPMS capabilities of Derby are problematic. So I would be glad if anybody who knows what to do could guide me through the jungle. Cheers, Patrick
