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/HeadlessApplicationTest.java
assertNotNull(firstPart);
		MPart secondPart = getSecondPart();
		assertNotNull(secondPart);
		assertFalse(firstPart.equals(secondPart));
		return new MPart[] { firstPart, secondPart };
	}
	protected abstract MPart getFirstPart();
	protected abstract MPart getSecondPart();
	protected void createGUI(MUIElement uiRoot) {
		renderer.createGui(uiRoot);
	}
	@Override
	protected MApplicationElement createApplicationElement(
			IEclipseContext appContext) throws Exception {
		return createApplication(appContext, getURI());
	}
	protected abstract String getURI();
	protected IPresentationEngine createPresentationEngine(
			String renderingEngineURI) throws Exception {
		IContributionFactory contributionFactory = (IContributionFactory) applicationContext
				.get(IContributionFactory.class.getName());
		Object newEngine = contributionFactory.create(renderingEngineURI,
				applicationContext);
		return (IPresentationEngine) newEngine;
	}
	private MApplication createApplication(IEclipseContext appContext,
			String appURI) throws Exception {
		URI initialWorkbenchDefinitionInstance = URI.createPlatformPluginURI(
				appURI, true);
		ResourceSet set = new ResourceSetImpl();