OSGI manifests and existing packages

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

OSGI manifests and existing packages

Alistair Bush-2
Hi guys

Please be aware that the work Matt has been doing on eclipse-sdk:3.5 means
that we no longer have to modify (for 3.5 at least) eclipses dependencies to
include osgi headers in the manifest.

What happens in eclipse-sdk:3.5 is..

Matt Whitlock wrote:

> My ebuild does use system-installed packages.  It does this by unpacking
>  the metadata from the bundled JARs and modifying their classpaths so they
>  point to symlinks to the system-installed JARs.  Look in the
>  subdirectories of /usr/lib64/eclipse-3.5/plugins.  As an example, the
>  first one, ICU4J, has the following files:
>
>         META-INF/MANIFEST.MF
>         icu4j-charsets.jar -> /usr/share/icu4j-4/lib/icu4j-charsets.jar
>         icu4j.jar -> /usr/share/icu4j-4/lib/icu4j.jar
>         plugin.properties
>
> And the META-INF/MANIFEST.MF has this line in it (among others):
>
>         Bundle-ClassPath: icu4j-charsets.jar,icu4j.jar
>
> These few metadata files replace the big "com.ibm.icu_4.0.1.v20090822.jar"
>  blob that comes bundled with Eclipse.
>

We should continue maintaining these headers until 3.5 is stabilised, once
this happens they can be removed.

I plan on moving eclipse-sdk:3.5 into the tree this week.  There are some
things that I would like to be done.  (see [1]) but I believe that this ebuild
is far better than the current one so i'm prepared to compromise.

As an example we currently build against bundled jars and then replace them
with system jars.

If anyone has any objections then please speak up.

Thanks

Alistair.

ps.  Currently I'm singing Matt's praises from the rafters, please join me.


[1] https://bugs.gentoo.org/show_bug.cgi?id=296296

Reply | Threaded
Open this post in threaded view
|

Re: OSGI manifests and existing packages

Jean-Noël Rivasseau-4
Hi,

Yes first and foremost I want to thank Matt for the awesome work he has put into Eclipse while the official maintainer was slacking on it (Matt, that would be me...)

I've still been watching the bug from time to time and actually wanted to contact Matt myself too, since it seemed to me the ebuild reached enough maturity to be included in the main tree. ali_bush beat me to it and that is fine, since my company (plus a recent move to Canada) is still eating up my time, so the ebuild will probably move faster to the tree if ali_bush handles it.

I would be interested in learning all the details of the new ebuild but I am pretty sure that yes it is far better than the current one (which is a good thing; eclipse ebuilds have been constantly improved from the 3.2 one which was horrible, all bundled etc).

ali_bush, you mention that we currently build against the bundled jars, I don't think that's actually true (I would have to double check but I think we build against systeme packages...)

Elvanor

On Wed, Dec 9, 2009 at 2:51 AM, Alistair Bush <[hidden email]> wrote:
Hi guys

Please be aware that the work Matt has been doing on eclipse-sdk:3.5 means
that we no longer have to modify (for 3.5 at least) eclipses dependencies to
include osgi headers in the manifest.

What happens in eclipse-sdk:3.5 is..

Matt Whitlock wrote:
> My ebuild does use system-installed packages.  It does this by unpacking
>  the metadata from the bundled JARs and modifying their classpaths so they
>  point to symlinks to the system-installed JARs.  Look in the
>  subdirectories of /usr/lib64/eclipse-3.5/plugins.  As an example, the
>  first one, ICU4J, has the following files:
>
>         META-INF/MANIFEST.MF
>         icu4j-charsets.jar -> /usr/share/icu4j-4/lib/icu4j-charsets.jar
>         icu4j.jar -> /usr/share/icu4j-4/lib/icu4j.jar
>         plugin.properties
>
> And the META-INF/MANIFEST.MF has this line in it (among others):
>
>         Bundle-ClassPath: icu4j-charsets.jar,icu4j.jar
>
> These few metadata files replace the big "com.ibm.icu_4.0.1.v20090822.jar"
>  blob that comes bundled with Eclipse.
>

We should continue maintaining these headers until 3.5 is stabilised, once
this happens they can be removed.

I plan on moving eclipse-sdk:3.5 into the tree this week.  There are some
things that I would like to be done.  (see [1]) but I believe that this ebuild
is far better than the current one so i'm prepared to compromise.

As an example we currently build against bundled jars and then replace them
with system jars.

If anyone has any objections then please speak up.

Thanks

Alistair.

ps.  Currently I'm singing Matt's praises from the rafters, please join me.


[1] https://bugs.gentoo.org/show_bug.cgi?id=296296
Reply | Threaded
Open this post in threaded view
|

Re: OSGI manifests and existing packages

Alistair Bush-2
> Hi,
>
> Yes first and foremost I want to thank Matt for the awesome work he has put
> into Eclipse while the official maintainer was slacking on it (Matt, that
> would be me...)
>
> I would be interested in learning all the details of the new ebuild but I
>  am pretty sure that yes it is far better than the current one (which is a
>  good thing; eclipse ebuilds have been constantly improved from the 3.2 one
>  which was horrible, all bundled etc).

Have a look at linuxtools-dev at eclipse.  They are doing a fantastic job and
are really cleaning up the way eclipse is built.  Believe there is even
support for running the unit tests.  It uses vnc or something so we maybe able
to run GUI tests in the ebuilds ( or at least thats the hope ).

>
> ali_bush, you mention that we currently build against the bundled jars, I
> don't think that's actually true (I would have to double check but I think
> we build against systeme packages...)
>

Yes I believe the current 3.4.1 ebuild does,  but not 3.5.1. I, at least, I
can see no indication of it.

> Elvanor
>
> On Wed, Dec 9, 2009 at 2:51 AM, Alistair Bush <[hidden email]> wrote:
> > Hi guys
> >
> > Please be aware that the work Matt has been doing on eclipse-sdk:3.5
> > means that we no longer have to modify (for 3.5 at least) eclipses
> > dependencies to
> > include osgi headers in the manifest.
> >
> > What happens in eclipse-sdk:3.5 is..
> >
> > Matt Whitlock wrote:
> > > My ebuild does use system-installed packages.  It does this by
> > > unpacking the metadata from the bundled JARs and modifying their
> > > classpaths so
> >
> > they
> >
> > >  point to symlinks to the system-installed JARs.  Look in the
> > >  subdirectories of /usr/lib64/eclipse-3.5/plugins.  As an example, the
> > >  first one, ICU4J, has the following files:
> > >
> > >         META-INF/MANIFEST.MF
> > >         icu4j-charsets.jar -> /usr/share/icu4j-4/lib/icu4j-charsets.jar
> > >         icu4j.jar -> /usr/share/icu4j-4/lib/icu4j.jar
> > >         plugin.properties
> > >
> > > And the META-INF/MANIFEST.MF has this line in it (among others):
> > >
> > >         Bundle-ClassPath: icu4j-charsets.jar,icu4j.jar
> > >
> > > These few metadata files replace the big
> >
> > "com.ibm.icu_4.0.1.v20090822.jar"
> >
> > >  blob that comes bundled with Eclipse.
> >
> > We should continue maintaining these headers until 3.5 is stabilised,
> > once this happens they can be removed.
> >
> > I plan on moving eclipse-sdk:3.5 into the tree this week.  There are some
> > things that I would like to be done.  (see [1]) but I believe that this
> > ebuild
> > is far better than the current one so i'm prepared to compromise.
> >
> > As an example we currently build against bundled jars and then replace
> > them with system jars.
> >
> > If anyone has any objections then please speak up.
> >
> > Thanks
> >
> > Alistair.
> >
> > ps.  Currently I'm singing Matt's praises from the rafters, please join
> > me.
> >
> >
> > [1] https://bugs.gentoo.org/show_bug.cgi?id=296296
>