Tracer Plugin is not loaded when needed

[lschuetze]

Eclipse uses a lazy activation mechanism to load plugins. This causes the tracer plugin to not be loaded when the interpretation is started and therefor causes the tracer view not to show any interpretation results.

The cause is due to inversion of control. Since the tracer registers itself as a listener to the interpreter it needs to be started before the interpretation process is starting. Due ot the lazy activation this is not possible without adding dependencies to the interpreter. This should be avoided under all circumstances (since the tracer plugin uses the interpreter we would have circular dependencies).

Is there any mechanism within Eclipse to avoid this issue? There is the IStartup Interface but that would cause the tracer to be loaded (and so all its dependencies). First, this causes Eclipse to use much more memory as necessary and second it increases the startup time of Eclipse unnecessarily.

Since Eclipse Juno, there is the ability to use dependency injection. This need to be investigated whether it is an appropriate solution to solve this issue.