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/workbench/RenderingTestCase.java
.getServiceContext(Activator.getDefault().getBundle()
					.getBundleContext());
	protected static MApplication app = MApplicationFactory.eINSTANCE
			.createApplication();
	protected static Display display = Display.getCurrent() != null ? Display
			.getCurrent() : new Display();
	
	protected IPresentationEngine renderer;
	protected IEclipseContext appContext;
	protected Widget topWidget;
	protected long startTime;
	/**
	 * Test cases derived from this class are used to test the Model <-> (SWT)
	 * UI relationships. These tests will ensure that the correct controls are
	 * created and that the various listeners (data bindings...) behave
	 * correctly.
	 */
	public RenderingTestCase() {
	}
	/*
	 * (non-Javadoc)
	 * 
	 * @see junit.framework.TestCase#setUp()
	 */
	@Override
	protected void setUp() throws Exception {
		System.out.println("Setup");
		startTime = System.currentTimeMillis();
		super.setUp();