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/EPartServiceTest.java
ClientEditor editor = (ClientEditor) saveablePart.getObject();
		editor.setThrowException(throwException);
		
		applicationContext.set(ISaveHandler.class.getName(), null);
		EPartService partService = (EPartService) window.getContext().get(
				EPartService.class.getName());
		if (beforeDirty) {
			assertEquals(!throwException, partService.savePart(saveablePart,
					confirm));
		} else {
			assertTrue(
					"The part is not dirty, the save operation should have complete successfully",
					partService.savePart(saveablePart, confirm));
		}
		assertEquals(beforeDirty && throwException, saveablePart.isDirty());
		assertEquals(beforeDirty, editor.wasSaveCalled());
	}
	public void testSavePart_NoHandler_TTT() {
		testSavePart_NoHandler(true, true, true);
	}
	public void testSavePart_NoHandler_TTF() {
		testSavePart_NoHandler(true, true, false);
	}
	public void testSavePart_NoHandler_TFT() {
		testSavePart_NoHandler(true, false, true);
	}
	public void testSavePart_NoHandler_TFF() {
		testSavePart_NoHandler(true, false, false);
	}
	public void testSavePart_NoHandler_FTT() {