On Sat, 23 Oct 2021 at 07:28, Jaroslav Tulach <[email protected]> wrote: > but I am not going to propose changes to the way we deliver nb-javac to > users.
Why?! Is anyone here suggesting we shouldn't deliver nb-javac by default to users? Please don't drop that plan - I didn't spend a load of time arguing the legal point to want to stick with the status quo! :-) We just need some way to meet the needs of people who want to run against JDK javac for whatever reason. I wonder if the baseline for running without nb-javac could be raised to JDK 17 and still meet requirements mentioned here? That might help with the testing matrix concerns? > > I'm also hoping if/when we do include nb-javac by default, it will > > never again be a cause of release delays! :-) > > Of course. Generating new nb-javac binary shall be matter of changing few > lines of code and pressing the build button. Yes, but not by us. All we can do at ASF is consume the produced and distributed binaries*. If you / OracleLabs (ideally), is taking this process on and ensuring more responsive timing, great! It's still not a process we have any control over here. * OK, if the patch files were all ASL licensed we *might* be able to find a way to do this as part of the NetBeans build I guess? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
