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/application/ESelectionServiceTest.java
private IPresentationEngine getEngine() {
		if (engine == null) {
			IContributionFactory contributionFactory = (IContributionFactory) applicationContext
					.get(IContributionFactory.class.getName());
			Object newEngine = contributionFactory.create(getEngineURI(),
					applicationContext);
			assertTrue(newEngine instanceof IPresentationEngine);
			applicationContext.set(IPresentationEngine.class.getName(),
					newEngine);
			engine = (IPresentationEngine) newEngine;
		}
		return engine;
	}
	public void testGetSelection() {
		MApplication application = MApplicationFactory.eINSTANCE
				.createApplication();
		MWindow window = MApplicationFactory.eINSTANCE.createWindow();
		application.getChildren().add(window);
		application.setSelectedElement(window);
		MPart partA = MApplicationFactory.eINSTANCE.createPart();
		partA.setId("partA"); 
		window.getChildren().add(partA);
		window.setSelectedElement(partA);
		MPart partB = MApplicationFactory.eINSTANCE.createPart();
		partB.setId("partB"); 
		window.getChildren().add(partB);
		initialize(applicationContext, application);
		getEngine().createGui(window);
		IEclipseContext contextA = partA.getContext();
		IEclipseContext contextB = partB.getContext();