mbien commented on pull request #3206: URL: https://github.com/apache/netbeans/pull/3206#issuecomment-952239996
> @mbien: The range of JDKs our users use is broad. Considering just JDK17, even minor changes in javac in its patch releases can potentially affect IDE's operation. With bundled Javac (e.g. the automatically generated one), Apache NetBeans controls (and can test before update) what version will be shipped with a release. We have no such control over user's execution evnironmnet. If we do some magic depending on the actual runtime of the user, the user may face "random" errors depending on automatic OS updates (newer JDK patch release installed) etc. > > I am against introducing such magic, and if so, it should be opt-in, not the default. Thanks for answering. Thats actually the first time i got an answer for that question. The concern is that a JDK update release could introduce incompatible changes, so it is safer to run nb-javac N on JDK N instead of using the JDK's compiler - understood, However, if it is undesired to provide a way to conditionally disable nb-javac for N+1 too, it will make it impossible to test upstream JDK versions unfortunately, since NB will use the backported javac instead of the compatible one, I used NB for it so far since it made sense to run an IDE which also uses the compiler of the underlying ea JDK you want to test, but there are other options. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- 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
