po 22. 3. 2021 v 16:22 odesÃlatel Neil C Smith <neilcsm...@apache.org> napsal:
> On Mon, 22 Mar 2021 at 15:01, Laszlo Kishalmi <laszlo.kisha...@gmail.com> > wrote: > > Is there an NBM available to try this one out? > > +1! :-) > There is a pull request: https://github.com/apache/netbeans/pull/2801 - I am trying to help with it as much as I can and provide some guidance. There is however still tons of failures mostly because nb-javac and upstream javac are: - treated differently - tested differently - known to behave differently - known to be differently buggy We are wasting time maintaining two different lines of code and none of them works well! All of that makes me more and more convinced: It is really essential for the Apache NetBeans project to stop using the manually crafted NbJavac as soon as 12.4 is out! NetBeans IDE 12.5 should require: - either run the IDE on JDK17 for Java related development - or install modern nbjavac automatically converted with the help of [advanced refactorings](https://github.com/oracle/nb-javac/pull/12) E.g. implement the plan as outlined at https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac > Telling the truth the javac integration in 12.3 became really unstable, > ... > We have lots of issues reported on them in JIRA as well. In my opinion, throwing away the "two paths to (parse and) access Javac ASTs" is going to help us improving the quality. It will finally be clear that "Javac from the latest JDK" is the reference implementation of NetBeans IDE "parser" that we have to optimize for, bugfix for and develop against. -jt PS: If we could also get LEGAL-563 permission in 13.0 LTS timeframe, that would be magnificent!
