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
public Object otherSelection;
		public void setOtherSelection(Object selection) {
			otherSelection = selection;
		}
	}
	static class UseSelectionHandler {
		public Object selection;
		public void execute(
				@Optional @Named(ESelectionService.SELECTION) Object s) {
			selection = s;
		}
	}
	public void testOnePartSelection() throws Exception {
		MApplication application = MApplicationFactory.eINSTANCE
				.createApplication();
		MWindow window = MApplicationFactory.eINSTANCE.createWindow();
		application.getChildren().add(window);
		application.setSelectedElement(window);
		initialize(applicationContext, application);
		getEngine().createGui(window);
		ProviderPart p = new ProviderPart();
		ContextInjectionFactory.inject(p, window.getContext());
		assertNull(p.input);
		Object selection = new Object();