I must add that a sign of a big breakthrough in NetBeans progress is historically always right at the point of my greatest despair — which is good because that point is now: we’ve missed our release date, might not make it at all this month, which will have knock on effects.
I propose we accept Neil’s minimal solution that at least solves the problem, that Eric includes it in a beta 5 to be released by Monday, and that we use that to start voting immediately, aiming in a very best case scenario to release end of next week. Gj On Wed, 20 May 2020 at 23:41, Geertjan Wielenga <[email protected]> wrote: > Yeah, I don't think we should discuss anymore if but how this should be > fixed, especially given this is an LTS release. > > Gj > > On Wed, May 20, 2020 at 11:24 PM Neil C Smith <[email protected]> > wrote: > >> On Wed, 20 May 2020, 20:09 Matthias Bläsing, <[email protected]> >> wrote: >> >> > this is not true. The problem exist since the first release of Apache >> > NetBeans. nbjavac was required on all JDKs and is now required on JDK >> > 8. >> >> >> It is true if we're talking about the same thing - nb-javac has never been >> required *via ergonomics* on any JDK but 8. See >> https://github.com/apache/netbeans/pull/715 >> >> Yes, the same bug potentially affects JDK 8 with nb-javac too. Although my >> proposed change would stop it erroring there too. >> >> >> > With the addition of JavaFX the situation got a bit worse, but only >> > gradually. If we could just bundle our dependencies ... >> > >> >> We are in agreement here, but right now that's not an option ... >> >> >> > The download for JavaFX comes from maven central (yes I know, that even >> > maven central is down at times). >> > >> >> True! But network problems don't just apply to the server end. Because >> this >> effectively brings nb-javac along for the required ride too, I think >> failures to download that also come into play, judging from some reports. >> >> >> > From my perspective NetBeans works as well as for example a maven build >> > works, that has dependencies not yet present in a local repository. >> > >> >> Good! I'm sure the people who have reported issues or been confused by >> this >> are happy about that. ;-) It's not a problem for me either because I know >> how to work around it. But comparing Maven to a GUI that effectively locks >> up isn't a fair one. >> >> I noticed this issue when trying to test JDK 14 and it surprised me, so I >> went looking for reports, and found a few. Given it has only been a >> problem >> since 11.3, I'd expect more if we release with 12.0. It's been the problem >> behind two threads on users@ in the last 24 hours. >> >> Best wishes, >> >> Neil >> >> > >> >
