Community
Participate
Working Groups
Hi in 1 project i get this error: The type org.eclipse.core.expressions.Expression cannot be resolved. It is indirectly referenced from required .class files VisualFormEditor.java /com.servoy.eclipse.designer/src/com/servoy/eclipse/designer/editor line 638 Java Problem the method/line that errors is on is: public void activateEditorContext() { if (activateContext == null) { IContextService service = (IContextService)getSite().getService(IContextService.class); activateContext = service.activateContext(COM_SERVOY_ECLIPSE_DESIGNER_CONTEXT); } } its on the activeContext line. When i change another java file in another project (that project that generates the error is dependend on that one) Both project are plugins. For example the thing i change is: public synchronized Relation getRelation(String name) to public synchronized Relation getRelationa(String name) then i have the compile error then i change it to: public synchronized Relation getRelationab(String name) compile error in the other project is gone. and this toggle goes on and on. If i have the compile error and i clean only that project that has that error it also goes away (but then the next change and the toggling starts again) I have this behavior in 2 workspaces, 1 that is trunk and the other a branch workspace. Both have the +/- the same projects only branch has a few less and less other projects that dont have anything to do with these 2 projects/plugins My co worker has the same thing on his linux machine, i am using build: I20090611-1540 I am affraid that i cant reproduce this behavior in a small setup.. :( I can try a bit more but i hope that that error tells enough
I would be good if we could get the complete test case for further investigation.
*** This bug has been marked as a duplicate of bug 278745 ***
i think it will be very hard for me to get a testcase for this. Maybe i can debug it myself somehow, will try This doesnt really sounds like a dub of 278745 why would you think it is?
Does your case compile successfully with 3.4.2 ? This is the same case as bug 278745 since IContextService defines 4 activateContext() methods. The one you're sending is IContextActivation activateContext(String contextId); But the other 3 take 2-3 parameters & one of which is Expression that is not on your classpath
Verified for 3.6M1 using build I20090803-1300