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 would be interested in learning all the details of the new ebuild but I |
8 |
> am pretty sure that yes it is far better than the current one (which is a |
9 |
> good thing; eclipse ebuilds have been constantly improved from the 3.2 one |
10 |
> which was horrible, all bundled etc). |
11 |
|
12 |
Have a look at linuxtools-dev at eclipse. They are doing a fantastic job and |
13 |
are really cleaning up the way eclipse is built. Believe there is even |
14 |
support for running the unit tests. It uses vnc or something so we maybe able |
15 |
to run GUI tests in the ebuilds ( or at least thats the hope ). |
16 |
|
17 |
> |
18 |
> ali_bush, you mention that we currently build against the bundled jars, I |
19 |
> don't think that's actually true (I would have to double check but I think |
20 |
> we build against systeme packages...) |
21 |
> |
22 |
|
23 |
Yes I believe the current 3.4.1 ebuild does, but not 3.5.1. I, at least, I |
24 |
can see no indication of it. |
25 |
|
26 |
> Elvanor |
27 |
> |
28 |
> On Wed, Dec 9, 2009 at 2:51 AM, Alistair Bush <ali_bush@g.o> wrote: |
29 |
> > Hi guys |
30 |
> > |
31 |
> > Please be aware that the work Matt has been doing on eclipse-sdk:3.5 |
32 |
> > means that we no longer have to modify (for 3.5 at least) eclipses |
33 |
> > dependencies to |
34 |
> > include osgi headers in the manifest. |
35 |
> > |
36 |
> > What happens in eclipse-sdk:3.5 is.. |
37 |
> > |
38 |
> > Matt Whitlock wrote: |
39 |
> > > My ebuild does use system-installed packages. It does this by |
40 |
> > > unpacking the metadata from the bundled JARs and modifying their |
41 |
> > > classpaths so |
42 |
> > |
43 |
> > they |
44 |
> > |
45 |
> > > point to symlinks to the system-installed JARs. Look in the |
46 |
> > > subdirectories of /usr/lib64/eclipse-3.5/plugins. As an example, the |
47 |
> > > first one, ICU4J, has the following files: |
48 |
> > > |
49 |
> > > META-INF/MANIFEST.MF |
50 |
> > > icu4j-charsets.jar -> /usr/share/icu4j-4/lib/icu4j-charsets.jar |
51 |
> > > icu4j.jar -> /usr/share/icu4j-4/lib/icu4j.jar |
52 |
> > > plugin.properties |
53 |
> > > |
54 |
> > > And the META-INF/MANIFEST.MF has this line in it (among others): |
55 |
> > > |
56 |
> > > Bundle-ClassPath: icu4j-charsets.jar,icu4j.jar |
57 |
> > > |
58 |
> > > These few metadata files replace the big |
59 |
> > |
60 |
> > "com.ibm.icu_4.0.1.v20090822.jar" |
61 |
> > |
62 |
> > > blob that comes bundled with Eclipse. |
63 |
> > |
64 |
> > We should continue maintaining these headers until 3.5 is stabilised, |
65 |
> > once this happens they can be removed. |
66 |
> > |
67 |
> > I plan on moving eclipse-sdk:3.5 into the tree this week. There are some |
68 |
> > things that I would like to be done. (see [1]) but I believe that this |
69 |
> > ebuild |
70 |
> > is far better than the current one so i'm prepared to compromise. |
71 |
> > |
72 |
> > As an example we currently build against bundled jars and then replace |
73 |
> > them with system jars. |
74 |
> > |
75 |
> > If anyone has any objections then please speak up. |
76 |
> > |
77 |
> > Thanks |
78 |
> > |
79 |
> > Alistair. |
80 |
> > |
81 |
> > ps. Currently I'm singing Matt's praises from the rafters, please join |
82 |
> > me. |
83 |
> > |
84 |
> > |
85 |
> > [1] https://bugs.gentoo.org/show_bug.cgi?id=296296 |
86 |
> |