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/HeadlessContextPresentationEngine.java
}
			parent = parent.getParent();
		}
		return context;
	}
	private static void populateModelInterfaces(MContext contextModel,
			IEclipseContext context, Class<?>[] interfaces) {
		for (Class<?> intf : interfaces) {
			Activator.trace(Policy.DEBUG_CONTEXTS,
					"Adding " + intf.getName() + " for " 
							+ contextModel.getClass().getName(), null);
			context.set(intf.getName(), contextModel);
			populateModelInterfaces(contextModel, context, intf.getInterfaces());
		}
	}
	@PostConstruct
	void postConstruct() {
		childHandler = new EventHandler() {
			public void handleEvent(Event event) {
				if (UIEvents.EventTypes.ADD.equals(event
						.getProperty(UIEvents.EventTags.TYPE))) {
					Object element = event
							.getProperty(UIEvents.EventTags.NEW_VALUE);
					if (element instanceof MUIElement) {
						Object parent = event
								.getProperty(UIEvents.EventTags.ELEMENT);
						createGui((MUIElement) element, parent);
						if (parent instanceof MPartStack) {
							MPartStack stack = (MPartStack) parent;
							List<MPart> children = stack.getChildren();