Community
Participate
Working Groups
Not a lot of data, but I wanted to log the problem anyways. Moved to core since the class loading is triggered by the indexer. The problem happend after I killed the workspace and then tried to restart it. The 2nd restart workded fine. Plugin org.eclipse.jdt.ui activation failed while loading class org.eclipse.jdt. internal.ui.JavaPerspectiveFactory org.eclipse.core.internal.boot.DelegatingURLClassLoader$DelegatingLoaderExceptio n: Attempt to load class org.eclipse.jdt.internal.core.search.indexing.AddJarFil eToIndex from deactivated plug-in org.eclipse.jdt.core. at org.eclipse.core.internal.plugins.PluginClassLoader.shouldLookForClas s(PluginClassLoader.java:200) at org.eclipse.core.internal.plugins.PluginClassLoader.findClassParentsS elf(PluginClassLoader.java(Compiled Code)) at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(Del egatingURLClassLoader.java(Compiled Code)) at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(Del egatingURLClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexJarFi le(IndexManager.java:384) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexAll(I ndexManager.java:236) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.checkIndex Consistency(IndexManager.java:94) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.activatePr ocessing(IndexManager.java:52) at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobMan ager.java:247) at java.lang.Thread.run(Thread.java:498)
This sounds more like a Platform/Core issue. The only interesting factor in the JDT/Core indexer is that it starts working in background while the JDT/UI is loading (since JDT/Core is a prereq of JDT/UI).
I believe you are seeing expected plugin class loader behaviour. Here is what I believe to have happened: org.eclipse.jdt.core plugin threw some exception during activation (Plugin constructor or startup() method). This caused the plug-in to be deactivated. However, it had already succeeded in launching the indexer thread. When the indexer thread tried to load more classes, it failed because the JDT Core plugin had been deactivated. The real question is why the JDT Core startup threw an exception. There should have been a log entry for that. The strack trace included in this PR is really a side-effect of that original problem.
I pretty sure that the exception that has triggerd this walkback was caused by 5812. The problem happend to me in the same context.
Closed since referenced bug was fixed in a previous build. Will re-open if problem occurs again.
