Re: [equinox-dev] Why do we need systembundle.mf?

[Thomas Watson <tjwatson@xxxxxxxxxx>]

We use a /META-INF/MANIFEST.MF file
for the system bundle manifest to make it look as much like a normal bundle
as possible.  This helps us out for tooling because the org.eclipse.osgi
project looks just like any other bundle project to the tools.  The
content of the system bundle's manifest file is merged with some values
defined by the adaptors to allow them to add more stuff to the system bundle
(i.e export more packages).

With that said, I'm still not sure why
a systembundle.mf file helps you.  We still need to know where to
locate it.  Right now it is in the /META-INF directory of the org.eclipse.osgi
bundle.  This directory is not included on the classpath of the framework
so it cannot look for it by using Class.getResource().  We still must
be told where to locate the system bundle manifest file.  This is
currently done by looking at the system property "osgi.framework"
which is set to a file URL which specifies the location of the system bundle
(i.e path to org.eclipse.osgi).  If this property is not set then
we use the current working directory to look in.  If we cannot find
a manifest file then we start looking for a SYSTEMBUNDLE.MF.  But
the code only looks in the package org.eclipse.osgi.framework.adaptor.core
for a SYSTEMBUNDLE.MF resource.  Currently this file is not there
(it is in the /META-INF/ directory of the org.eclipse.osgi bundle) so it
fails to find it.  So in its currently location it is not useful.
 Glyn, maybe you are using a different configuration than I am?

Tom

Olivier Gruber/Watson/IBM@IBMUS
Sent by: equinox-dev-admin@xxxxxxxxxxx

01/27/2005 10:12 AM

Please respond to
equinox-dev

To	equinox-dev@xxxxxxxxxxx
cc	equinox-dev@xxxxxxxxxxx, equinox-dev-admin@xxxxxxxxxxx
Subject	Re: [equinox-dev] Why do we need systembundle.mf?

Renaming to a manifest.mf was a problem at one time.

There was an issue in locating that manifest.mf because there were other
such files 
on the classpath... can't remember the exact cause, but I remember that
we had the 
problem because the system bundle was loaded by a JRE-provided classloader,
not a bundle classloader... 

I don't know if it is still an issue. 
Cheers,

Olivier Gruber, Ph.D.
Persistent & Distributed Object Platforms and Frameworks
IBM TJ Watson Research Center

Jeff McAffer <Jeff_McAffer@xxxxxxxxxx> Sent by: equinox-dev-admin@xxxxxxxxxxx 01/27/2005 09:45 AM Please respond to equinox-dev

To:        equinox-dev@xxxxxxxxxxx        cc:                Subject:        Re: [equinox-dev] Why do we need systembundle.mf?

Is it that you want to delete the file or rename it to manifest.mf?  Seems
like the file is actually required as it has lots of exports etc.  If
you delete it then the adaptor would have to supply all that info.  I
think the model was that the systembundle.mf combined with the relevant
adaptor.mfs gives the logical manifest.mf for the system bundle.  Having
an actual manifest.mf for the system bundle might be confusing.

Jeff

Glyn Normington <glyn_normington@xxxxxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx

01/27/2005 07:17 AM

Please respond to
equinox-dev

To	equinox-dev@xxxxxxxxxxx
cc
Subject	Re: [equinox-dev] Why do we need systembundle.mf?

>I can't find a reason as why we still have systembundle.mf in the
framework.

It enables the OSGi framework to be started outside of Eclipse without
the
user having to provide their own system bundle manifest, which is just
one
less step in getting started.

Glyn

Telephone: +44-(0)1962-815826. Email: glyn_normington@xxxxxxxxxx

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/equinox-dev