Thanks, I think I got it now. Ended up at https://github.com/apache/netbeans/blob/master/platform/core.output2/src/org/netbeans/core/output2/NbIOProvider.java . I also think I understand why there are, at least, two IOProviders, and the main problem was resolved by adding a missing dependency.
So far it's a happy new year. :) Den tis 31 dec. 2019 kl 16:50 skrev Emilian Bold <emilian.b...@gmail.com>: > IOProvider.getDefault does return the first match in the global lookup if > you look at the source. > > --emi > > mar., 31 dec. 2019, 16:41 Patrik Karlström <pat...@trixon.se> a scris: > >> Well, I have always used IOProvider.getDefault() but I'll have a look at >> doing it via lookup, that might solve the actual problem too. >> >> Den tis 31 dec. 2019 kl 15:12 skrev Emilian Bold <emilian.b...@gmail.com >> >: >> >>> My guess the first one in the Lookup? Why would you pick which service >>> to use? >>> >>> --emi >>> >>> On Tue, Dec 31, 2019 at 4:00 PM Patrik Karlström <pat...@trixon.se> >>> wrote: >>> > >>> > While trying to solve a problem related to class loading >>> ClassNotFoundException ... starting from ... >>> > I noticed that there are actually two IOProviders available, one in >>> org.netbeans.api.io and the other one in org.openide.windows. How come? >>> > They are similar, but not identical. >>> > >>> > Any guidelines on which to use? >>> > >>> >>
