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.swt/src/org/eclipse/e4/ui/workbench/swt/internal/E4Application.java
return args[i + 1];
		}
		return appContext.getBrandingProperty(argName);
	}
	public void stop() {
	}
	public static IEclipseContext createDefaultContext() {
		return createDefaultContext(null);
	}
	public static IEclipseContext createDefaultContext(
			IEclipseContextStrategy strategy) {
		
		
		
		IEclipseContext serviceContext = E4Workbench.getServiceContext();
		final IEclipseContext appContext = EclipseContextFactory.create(
				serviceContext, strategy);
		appContext.set(IContextConstants.DEBUG_STRING, "WorkbenchAppContext"); 
		
		IExtensionRegistry registry = RegistryFactory.getRegistry();
		ExceptionHandler exceptionHandler = new ExceptionHandler();
		ReflectionContributionFactory contributionFactory = new ReflectionContributionFactory(
				registry);
		appContext.set(IContributionFactory.class.getName(),
				contributionFactory);
		appContext.set(Logger.class.getName(), ContextInjectionFactory.inject(
				new WorkbenchLogger(), appContext));
		appContext.set(Adapter.class.getName(), ContextInjectionFactory.inject(
				new EclipseAdapter(), appContext));
		appContext.set(IContextConstants.DEBUG_STRING, "WorkbenchContext");