Community
Participate
Working Groups
Build Identifier: M20110909-1335 This problem should either be detected at compile time or should not cause a runtime error at all. Reproducible: Always Steps to Reproduce: 1. Create plugin A. 2. Create class SUPER in package P. 3. Create protected method M in SUPER. 4. Create plugin B. 5. Create class SUB derived from SUPER in package P. 6. Create inner class INNER in SUB. 7. Create method N in INNER that calls the method M in SUB inherited from SUPER.
Please attach the stack trace here for more details. Thanks.
Please attach a small test case that shows the problem. Unless it is absolutely needed, eliminate plugins and all eclipse'isms and provide a stand alone java test case. If you are able to put together a small java test case, document how the latest javac compiler behaves, TIA.
Here is a stack trace: java.lang.IllegalAccessError: tried to access method p.Super.m()V from class p.Sub$1 at p.Sub$1.run(Sub.java:10) at p.Sub.test(Sub.java:12) at p.Sub.earlyStartup(Sub.java:17) at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87) at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.Workbench$63.run(Workbench.java:2465) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Created attachment 207403 [details] Two simple eclipse plugins triggering the bug
(In reply to comment #4) > Created attachment 207403 [details] > Two simple eclipse plugins triggering the bug Thanks, I'll take a look.
Same issue as bug 152568 which was closed as WONTFIX. *** This bug has been marked as a duplicate of bug 152568 ***
Verified for 3.8M5