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
null);
		assertEquals(selection, handler.selection);
		handler.selection = null;
		ContextInjectionFactory.invoke(handler, "execute", windowContext, null);
		assertEquals(selection, handler.selection);
		handler.selection = null;
		ContextInjectionFactory.invoke(handler, "execute", partContextA, null);
		assertEquals(selection, handler.selection);
		handler.selection = null;
		ContextInjectionFactory.invoke(handler, "execute", partContextB, null);
		assertNull(handler.selection);
		EPartService partService = (EPartService) windowContext
				.get(EPartService.class.getName());
		partService.activate(partB);
		ContextInjectionFactory.invoke(handler, "execute", applicationContext,
				null);
		assertNull(handler.selection);
		handler.selection = null;
		ContextInjectionFactory.invoke(handler, "execute", windowContext, null);
		assertNull(handler.selection);
		handler.selection = null;
		ContextInjectionFactory.invoke(handler, "execute", partContextA, null);
		assertEquals(selection, handler.selection);
		handler.selection = null;
		ContextInjectionFactory.invoke(handler, "execute", partContextB, null);
		assertNull(handler.selection);
	}
	public void testThreePartSelection() throws Exception {
		MApplication application = MApplicationFactory.eINSTANCE
				.createApplication();