Hi, On Sun, 7 Mar 2021 at 18:39, Jaroslav Tulach <jaroslav.tul...@gmail.com> wrote: > Please join me in > reviewing and discussing the consequences for NetBeans here or in the PR#12: > > https://github.com/oracle/nb-javac/pull/12 > > Manually written nb-javac is dead. Long live the new nb-javac!
Firstly, let me say I think that's a great move forward for nb-javac. And from how I worded that, you probably know I'm going to raise a "however" .. :-) Not something that might be a showstopper to us learning to love nb-javac though .. > > Let's develop the new `nb-javac` and let's learn to love it! We need to unpick that sentence into two parts. If we presume "Let's develop" means Let *us* develop, then the simple answer is we can't. Development of nb-javac has to be external and independent. At the same time, in my experience from release managing, nb-javac has been the number one cause of release delays. Somehow those things need to be reconciled. In order to love nb-javac, surely we would need a long term, external commitment to develop it, and a surety that the external project can meet our release requirements? And I realise that "external" there is probably going to be mostly if not exclusively run by people who also happen to be NetBeans committers or PMC, just not here! Assuming that, then can we learn to love it? Well, firstly, as you're looking at the sources, an audit that every file is really subject to CPE *may* actually allow, given more recent developments, us to go back to Apache Legal and request permission to ship nb-javac as a dependency out of the box. Is that actually a desirable outcome, particularly considering above? If it remains an optional dependency, then we're left with considering "Optional means that the component is not required for standard use of the product or for the product to achieve a desirable level of quality. The question to ask yourself in this situation is: Will the majority of users want to use my product without adding the optional components?" Beyond JDK 17 do we consider compile on save a niche feature? Well, I'd like a global switch for it, so maybe! :-) What about editing JDK 19 while running on JDK 17? Could that also be addressed by eating our own dog food and running the LSP on the target VM? The key thing being, if nb-javac remains optional, then what features of the IDE do we continue to consider non-standard or not wanted by the majority of users? Contrary to the assertion, I'm not sure that everyone hates nb-javac. I don't! I think we've been staring at a map for a good long while, may have finally reached the fork in the road that we could see on the horizon, and are still not quite sure which direction to take. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
