Community
Participate
Working Groups
After updating eclipse to 2020-12 I am unable to launch junit tests and tomcat server instances. The same problem has already been posted at stackoverflow: https://stackoverflow.com/questions/65676277/eclipse-unable-to-instantiate-class-javasourcelookupdirector-expecting-stackma Error Message: Plug-in "org.eclipse.jdt.launching" was unable to instantiate class "org.eclipse.jdt.internal.launching.JavaSourceLookupDirector". Expecting a stackmap frame at branch target 53 Exception Details: Location: org/eclipse/debug/core/sourcelookup/AbstractSourceLookupDirector.dispose()V @29: goto Reason: Expected stackmap frame at this location. Bytecode: 0000000: b801 f9b6 01fa 4c2b 2ab9 022c 0200 2b2a 0000010: b902 2e02 002a b401 d6b6 01ef 4ea7 0018 0000020: 2db9 021b 0100 c001 004d 2c2a a500 092c 0000030: b902 3a01 002d b902 1a01 009a ffe5 2ab4 0000040: 01d6 b601 eb2a b401 dbc6 0026 2ab4 01db 0000050: 593a 05be 3604 033e a700 1119 051d 324d 0000060: 2cb9 0234 0100 8403 011d 1504 a1ff ef2a 0000070: 01b5 01db 2a01 b501 d7b1
This looks like some mismatch in plugins. Whats is the plugin versions for org.eclipse.jdt.launching and org.eclipse.debug.core?
3.19.0.v20201106-0848 org.eclipse.jdt.launching 3.17.0.v20201109-1948 org.eclipse.debug.core
(In reply to Manfred Weiss from comment #2) > 3.19.0.v20201106-0848 org.eclipse.jdt.launching > 3.17.0.v20201109-1948 org.eclipse.debug.core This looks fine. Can you try in a new workspace? Something looks corrupted. Also please provide the JDK details.
Created attachment 285350 [details] Screenshot
Same problem in a new empty workspace. Eclipse is running with "openjdk version 11.0.9.1 2020-11-04". The default JRE is "openjdk version 1.8.0_275" but the problem also occurs when using the same JRE as Eclipse is running with. Just found out that refactoring also does not work (see screenshot attached)
Looks like something went wrong in Update. Will you be able to install a fresh Eclipse 4.18 build and try?
A new installation works. But I opened the bug, because I am not the only one who has this problem. I would really like to find out what led to this problem.
Did you use Oomph or direct p2 repo for updating?
Direct p2 via the eclipse update site https://download.eclipse.org/releases/latest and Help -> Check for Updates
Can you please attach the Configuration details from the Eclipse SDK Installation details? Some dependent plug-in is not getting updated and we need to find that out.
Created attachment 285351 [details] Configuration details
(In reply to Manfred Weiss from comment #11) > Created attachment 285351 [details] > Configuration details I compared for the Eclipse SDK bundle but could not see any difference in plugin versions. Not sure how to proceed.
Probably the error log would be helpful. In the past there were occasionally problems after updates with bundle wiring, i.e., the wiring was incrementally updated which sometime produces different results from a new from-scratch wiring. Running from the command line with -clean forces the rewiring, so I would try that.
"-clean" did not solve the problem
In my case this error seems to have been caused by installing the Kotlin Plugin 0.8.21 from Eclipse Marketplace I was able to verify this by a step-by-step Eclipse setup process, as pointed out in my answer to the SO question. https://stackoverflow.com/a/66043188/5675083
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
