Community
Participate
Working Groups
I am working with the new AST support, however ASTParser states that to be able to resolve bindings it needs an IJavaProject instance. Calling org.aspectj.org.eclipse.jdt.core.JavaCore.create(IProject) causes the following exception to be thrown: java.lang.NoClassDefFoundError at org.aspectj.org.eclipse.jdt.core.JavaCore.create(JavaCore.java:1213) at org.eclipse.ajdt.internal.ui.viewsupport.SelectionListenerWithAJASTManager$PartListenerGroup.calculateASTandInform(SelectionListenerWithAJASTManager.java:173) at org.eclipse.ajdt.internal.ui.viewsupport.SelectionListenerWithAJASTManager$3.run(SelectionListenerWithAJASTManager.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) It would be nice to have this supported so that this feature of the AST can be used.
the 3.2 compiler allows AST manipulation without initializing projects and things... so this should be fixed when the 3.2compiler is integrated.
Is there a workaround for this problem with the current compiler, ie. a way to manualy intialize 'projects and things' before calling this method? Or do I have to wait for the new compiler to be integrated to get hold on AJ's version of ICompilationUnit? If I understand things correctly the latter is a prequisite for resolving type bindings in the AST tree. (See bug 146528)
I would also be interested in any workarounds possible, including something along the lines of setSource(char[]). I'd really like to build upon AJDT and this is blocking me.
The compiler upgrade may resolve this problem