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
assertTrue(part2.isToBeRendered());
		partService2.hidePart(part2);
		assertFalse(part1.isToBeRendered());
		assertFalse(part2.isToBeRendered());
	}
	private void testHidePart_Tagged(boolean tagged) {
		MApplication application = MApplicationFactory.eINSTANCE
				.createApplication();
		MWindow window = MApplicationFactory.eINSTANCE.createWindow();
		application.getChildren().add(window);
		application.setSelectedElement(window);
		MPart part = MApplicationFactory.eINSTANCE.createPart();
		window.getChildren().add(part);
		window.setSelectedElement(part);
		if (tagged) {
			part.getTags().add(EPartService.REMOVE_ON_HIDE_TAG);
		}
		initialize(applicationContext, application);
		getEngine().createGui(window);
		EPartService partService = (EPartService) window.getContext().get(
				EPartService.class.getName());
		partService.hidePart(part);
		assertFalse(part.isToBeRendered());
		assertEquals(tagged ? null : window, part.getParent());
	}
	public void testHidePart_Tagged_True() {
		testHidePart_Tagged(true);
	}
	public void testHidePart_Tagged_False() {
		testHidePart_Tagged(false);