Make the generated testing InjectorProvider more flexible

[LorenzoBettini]

Part of #3001

As hinted here #3001 (comment) instead of generating an injector provider of this shape:

protected MyDslRuntimeModule createRuntimeModule() {
	return new MyDslRuntimeModule() {
			@Override
			public ClassLoader bindClassLoaderToInstance() {
				return MyDslInjectorProvider.class
						.getClassLoader();
			}
	};
}

This PR generates it like that (main commit 1181731):

protected MyDslRuntimeModule createRuntimeModule() {
	return new MyDslRuntimeModule() {
			@Override
			public ClassLoader bindClassLoaderToInstance() {
				return MyDslInjectorProvider.this.getClass()
						.getClassLoader();
			}
	};
}

This section was introduced in the past for running tests in OSGI, e.g., by Maven Tycho, to get the correct class loader.

This new version makes the class loader be retrieved from the instance of the injector provider, NOT from the static class of the injector provider, as before.

Thus, simply inheriting an injector provider in another test bundle will make Guice take the correct class loader.

Instead, before, one had also to redefine the createRuntimeModule.

This makes things easier in testing. Some examples of simplification due to this change are:

• a85207c
• 7aeee04

I regenerated all our languages accordingly.

Concerning purexbase, I cleaned up things a bit 8230ada : the old RuntimeInjectorProvider was already useless, maybe something from the past.

The PR can be seen as a first step/preparation in case we want to address #3001

[szarnekow]

I think I like this. Small change and nice improvement.

[cdietrich]

find . -name "*InjectorProvider.java" | grep -v /ide/ | grep -v UiInjectorProvider | wc -l
108

 did you double check if you really regenerated all files?

[LorenzoBettini]

find . -name "*InjectorProvider.java" | grep -v /ide/ | grep -v UiInjectorProvider | wc -l 108

 did you double check if you really regenerated all files?

@cdietrich With "Quick Search" I searched for the string show_bug.cgi?id=493672 and regenerated the languages in each project with such an occurrence, so I should have caught them all. I haven't touched the injector providers that were not generated, but manually crafted, like XbaseInjectorProvider and the one of Xtend.

[cdietrich]

ok