On 07.05.24 13:33, Simon IJskes - QCG wrote:
Has any work been done to reproduce javac errors without an
interactive session?
well, netbeans has various tests which can run isolated bits of NB
functionality.
e.g
https://github.com/apache/netbeans/blob/master/java/refactoring.java/test/unit/src/org/netbeans/modules/refactoring/java/test/RenameTest.java
Any ideas on the amount of complexity to write a skeleton calling the
javac with the same parameters as NetBeans, in order to inspect
behaviour?
I experimented a bit with a javac sandbox project which did exactly that
to learn a more about the javac internals. But I got distracted with
other work and it has lower priority now.
Any ideas on the accesibility of the datastructures used, by for
instance the debugger or walking the data beforehand?
I mean you got a stack trace. You can set a break point in the
RenameRefactoringPlugin stack frame and start walking, going to be a
long walk though ;)
-mbien
Just freewheeling here. Ideally i could make this skeleton, run this
in NB, take my codebase, make some probe runs, and study behaviour.
Gr. Simon
---------------------------------------------------------------------
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
