Community
Participate
Working Groups
As the JavaModelManager is not aware of aspects, we cannot search for members in aspects or members in classes that have been introduced by aspects. Solving this problem would solve, or at least partially solve, many other problems like code completion or missing aj features in the package explorer view.
*** Bug 70212 has been marked as a duplicate of this bug. ***
This is partially solved now as we are inserting AJCompilationUnits into the JavaModel in 1.2.0 M1. We now get code completion proposals for elements defined in .aj files for example. But our elements can still not be found in JavaSearch or its underlying index. We can contribute to JavaSearch using the according extension point org.eclipse.jdt.ui.queryParticipant and I think that would be the next step to do to solve this bug. However, to get into the index itself, at least jdt bug 36939 needs to be dealt with. I am not sure though how desirable it is to get into the java index - maybe it is better to solve the related problems on another level.
hopefully addressed by jdt-weaving
Fixed with JDT weaving enabled.