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/ContextContentsTest.java
}
	private void testGet_IAdapterManager(IEclipseContext eclipseContext,
			boolean expected) {
		testGet(eclipseContext, IAdapterManager.class, expected);
	}
	public void testGet_IAdapterManager() {
		testGet_IAdapterManager(osgiContext, true);
		testGet_IAdapterManager(applicationContext, true);
	}
	public void testGet_Adapter() {
		testGet(osgiContext, Adapter.class, false);
		testGet(applicationContext, Adapter.class, true);
	}
	private void testGet_IPreferencesService(IEclipseContext eclipseContext,
			boolean expected) {
		testGet(eclipseContext, IPreferencesService.class, expected);
	}
	public void testGet_IPreferencesService() {
		testGet_IPreferencesService(osgiContext, true);
		testGet_IPreferencesService(applicationContext, true);
	}
	private void testGet_ISchedulingExecutor(IEclipseContext eclipseContext,
			boolean expected) {
		testGet(eclipseContext, ISchedulingExecutor.SERVICE_NAME, expected);
	}
	public void testGet_ISchedulingExecutor() {
		testGet_ISchedulingExecutor(osgiContext, true);
		testGet_ISchedulingExecutor(applicationContext, true);
	}
	private void testGet_IEventBroker(IEclipseContext eclipseContext,