mbien commented on issue #4766: URL: https://github.com/apache/netbeans/issues/4766#issuecomment-1336758619
first as warning: If the tone doesn't improve I will simply close this and move on. But since its Christmas time I am going to extend an olive branch: > Your suggestion does not make any sense because when I uninstall nb-javac then I remove the obvious culprit. It is not the obvious culprit. nb-javac is almost identical to javac except it's bytecode level, If the problem would be indeed gone by removing nb-javac 19b33 from the equation, all we would have to do is to regenerate nb-javac from latest javac of JDK 19. If the problem persists, we can ignore nb-javac and someone who is interested in this could try to fix it either in NB code which calls into javac or contribute a fix upstream in javac itself assuming it is reproducible. Turning nb-javac off and using the latest compatible javac is a fairly convenient and quick to execute method to exclude a whole category of possible causes from the get go. > Can you see how ridiculous your suggestion is? You seem to be clueless. Don't judge so fast otherwise it ends up being projection. You could have simply asked and I would have explained the reasoning behind the suggestion. -- 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
