Bug 304239 move each core application service to its own package
In M4, some services have their own package, others are provided in core.services. Boris and I talked about moving each service (API) to its own package. Reasons are: - aids with discoverability - helps separate application services from other public API in the core.services package (such as IDisposable, JSONObject) - helps to emphasize that services can be setup and consumed individually - will make it easier to move to separate bundles if that is ever needed This means moving Adapter, Logger, IStatusHandler to their own packages.
tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/RenderingTestCase.java
topWidget = null;
		}
		System.out.println("  time: "
				+ (System.currentTimeMillis() - startTime) + "ms");
	}
	protected void processEventLoop() {
		if (display != null) {
			while (display.readAndDispatch())
				;
		}
	}
	protected Widget createModel(final MWindow window) {
		MApplication application = (MApplication) appContext
				.get(MApplication.class.getName());
		application.getChildren().add(window);
		final Widget[] renderedObject = new Widget[1];
		renderedObject[0] = null;
		Realm.runWithDefault(SWTObservables.getRealm(display), new Runnable() {
			public void run() {
				
				
				renderer = (PartRenderingEngine) contributionFactory.create(
						PartRenderingEngine.engineURI, appContext);
				Object o = renderer.createGui(window);
				assertTrue("No widget rendered for: " + window.toString(),
						o != null);
				assertTrue("Rendered object is not a Widget: "
						+ o.getClass().getName(), o instanceof Widget);
				renderedObject[0] = (Widget) o;