Right. Deleting would be harsh. Depending on the configuration in which the framework is being run, that launcher may or may not be used. For example, in the Eclipse context, it is not needed. Its inclusion in the distribution opens alternate entry points which may not be desirable. The proposal here is to break it out into its own source folder and jar which may or may not be present. Eclipse would build without it, others would include it. Having a separate source folder simplifies the implementation of this setup.
Similarly, the classes in org.eclipse.osgi.framework.console (in the framework core project) appear to be optional. They are not referenced from anywhere other than the console implementation itself. Since it is not an integral part of the core, I suggest that it be broken out into its own source folder and so can be optionally included in a build.
Thomas Watson <tjwatson@xxxxxxxxxx>
09/25/2003 07:01 PM
To: Jeff McAffer/Ottawa/IBM@IBMCA
cc: equinox-dev@xxxxxxxxxxx, equinox-dev-admin@xxxxxxxxxxx
Subject: Re: [equinox-dev] launchers
We use the Launcher for starting the standard (non equinox) OSGi framework.
I think that this class should be included in the osgi core.