commit 99b918aa3e87f1a71652625de67e87084b3b928a
author Stephan Herrmann <stephan@cs.tu-berlin.de> Tue Sep 07 10:43:42 2010 +0000
committer Stephan Herrmann <stephan@cs.tu-berlin.de> Tue Sep 07 10:43:42 2010 +0000
tree 60cfe88d8ffc30bcd0972b402a61e32fb9a3bc5d
parent 8a3c6c100e8fe9e9800c64f6b4348746afb31aba

Avoid real work (here initializiing/setting classpath containers) during static initializers.
I saw deadlocks with involvment of the following stack-fragment:
        at org.eclipse.jdt.core.JavaCore.setClasspathVariable(JavaCore.java:4923)
        at org.eclipse.objectteams.otdt.core.ext.OTVariableInitializer.initialize(OTVariableInitializer.java:62)
        at org.eclipse.jdt.core.JavaCore.getClasspathVariable(JavaCore.java:2858)
        at org.eclipse.jdt.internal.core.JavaModelManager.getResolvedVariablePath(JavaModelManager.java:2411)
        at org.eclipse.jdt.core.JavaCore.getResolvedVariablePath(JavaCore.java:3400)
        at org.eclipse.objectteams.otdt.core.ext.OTDTPlugin.getResolvedVariablePath(OTDTPlugin.java:166)
        at org.eclipse.objectteams.otdt.core.ext.OTREContainer.<clinit>(OTREContainer.java:73)
        at org.eclipse.objectteams.otdt.core.ext.OTDTPlugin.start(OTDTPlugin.java:120)
(initializing BCEL_PATH early is OK, we need the BundleContext and don't perform further computations)