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.
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/ContributedPartRenderer.java
public Object createWidget(final MUIElement element, Object parent) {
		if (!(element instanceof MPart) || !(parent instanceof Composite))
			return null;
		Widget parentWidget = (Widget) parent;
		IEclipseContext parentContext = getContextForParent(element);
		Widget newWidget = null;
		final Composite newComposite = new Composite((Composite) parentWidget,
				SWT.NONE);
		newComposite.setLayout(new FillLayout());
		newWidget = newComposite;
		bindWidget(element, newWidget);
		final MPart part = (MPart) element;
		
		IEclipseContext localContext = E4Workbench.initializeContext(
				parentContext, part);
		E4Workbench.processHierarchy(part);
		IContributionFactory contributionFactory = (IContributionFactory) localContext
				.get(IContributionFactory.class.getName());
		localContext.set(Composite.class.getName(), newComposite);