Gentoo Archives: gentoo-java

From: "Jean-Noël Rivasseau" <elvanor@g.o>
To: Alistair Bush <ali_bush@g.o>
Cc: gentoo-java@l.g.o, Matt Whitlock <matt@××××××××.name>
Subject: Re: [gentoo-java] OSGI manifests and existing packages
Date: Wed, 09 Dec 2009 16:50:45
Message-Id: d61c57300912090850o2ab0ec5ck2687149d44454408@mail.gmail.com
In Reply to: [gentoo-java] OSGI manifests and existing packages by Alistair Bush
1 Hi,
2
3 Yes first and foremost I want to thank Matt for the awesome work he has put
4 into Eclipse while the official maintainer was slacking on it (Matt, that
5 would be me...)
6
7 I've still been watching the bug from time to time and actually wanted to
8 contact Matt myself too, since it seemed to me the ebuild reached enough
9 maturity to be included in the main tree. ali_bush beat me to it and that is
10 fine, since my company (plus a recent move to Canada) is still eating up my
11 time, so the ebuild will probably move faster to the tree if ali_bush
12 handles it.
13
14 I would be interested in learning all the details of the new ebuild but I am
15 pretty sure that yes it is far better than the current one (which is a good
16 thing; eclipse ebuilds have been constantly improved from the 3.2 one which
17 was horrible, all bundled etc).
18
19 ali_bush, you mention that we currently build against the bundled jars, I
20 don't think that's actually true (I would have to double check but I think
21 we build against systeme packages...)
22
23 Elvanor
24
25 On Wed, Dec 9, 2009 at 2:51 AM, Alistair Bush <ali_bush@g.o> wrote:
26
27 > Hi guys
28 >
29 > Please be aware that the work Matt has been doing on eclipse-sdk:3.5 means
30 > that we no longer have to modify (for 3.5 at least) eclipses dependencies
31 > to
32 > include osgi headers in the manifest.
33 >
34 > What happens in eclipse-sdk:3.5 is..
35 >
36 > Matt Whitlock wrote:
37 > > My ebuild does use system-installed packages. It does this by unpacking
38 > > the metadata from the bundled JARs and modifying their classpaths so
39 > they
40 > > point to symlinks to the system-installed JARs. Look in the
41 > > subdirectories of /usr/lib64/eclipse-3.5/plugins. As an example, the
42 > > first one, ICU4J, has the following files:
43 > >
44 > > META-INF/MANIFEST.MF
45 > > icu4j-charsets.jar -> /usr/share/icu4j-4/lib/icu4j-charsets.jar
46 > > icu4j.jar -> /usr/share/icu4j-4/lib/icu4j.jar
47 > > plugin.properties
48 > >
49 > > And the META-INF/MANIFEST.MF has this line in it (among others):
50 > >
51 > > Bundle-ClassPath: icu4j-charsets.jar,icu4j.jar
52 > >
53 > > These few metadata files replace the big
54 > "com.ibm.icu_4.0.1.v20090822.jar"
55 > > blob that comes bundled with Eclipse.
56 > >
57 >
58 > We should continue maintaining these headers until 3.5 is stabilised, once
59 > this happens they can be removed.
60 >
61 > I plan on moving eclipse-sdk:3.5 into the tree this week. There are some
62 > things that I would like to be done. (see [1]) but I believe that this
63 > ebuild
64 > is far better than the current one so i'm prepared to compromise.
65 >
66 > As an example we currently build against bundled jars and then replace them
67 > with system jars.
68 >
69 > If anyone has any objections then please speak up.
70 >
71 > Thanks
72 >
73 > Alistair.
74 >
75 > ps. Currently I'm singing Matt's praises from the rafters, please join me.
76 >
77 >
78 > [1] https://bugs.gentoo.org/show_bug.cgi?id=296296
79 >

Replies

Subject Author
Re: [gentoo-java] OSGI manifests and existing packages Alistair Bush <ali_bush@g.o>