[gentoo-java] Moving Eclipse-3.3 to tree

["Jean-Noël Rivasseau" <elvanor@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]

Hello all,

At this point all the dependencies for Eclipse were moved to main tree (they
use the osgi eclass so they make suitable jars for Eclipse). So there is
only now for Eclipse itself to be moved there.

Just wanted to check that junit-4.4-r1, which was also moved to tree, does
not trigger circular dependencies anymore (I checked on the bugzilla and it
seems it is ok).

For information I plan to move it as 3.3.1.1, deleting the ebuilds in the
experimental overlay except the ali_bush latest one (-r2).

Finally I need advice on the following (which is the only thing left to be
done on my agenda before putting Eclipse in tree):

I would like to offer the possibility for the user to control the Eclipse
startup options. Especially regarding the memory options as the default ones
make Eclipse run very slowly, crashing a lot especially on amd64.

Normally this is done by writing options to /usr/lib/eclipse-3.3/eclipse.ini,
but I was thinking of providing a configuration file in /etc/conf.d because:

1) It looks a better Gentoo way (eg, users know about /etc/conf.d, they may
not know about eclipse.ini)
2) It would have a simpler configuration syntax (pure familiar Bash syntax
resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the syntax in
the eclipse.ini file is more obscure even for me - looks like there should
be one option per line).

What is your feedback on this? Other options could include sourcing
~/.eclipserc, I don't like that much (it would create yet another .* file in
the home directory). Plus this is probably something to set globally on the
system.

However, I was wondering if /etc/conf.d would be appropriate for an
application's settings. Most of the stuff there is either server related
(tomcat, apache etc...) or system related (alsa, clock, xdm...)

Thanks for the feedback, Elvanör

[-- Attachment #2: Type: text/html, Size: 1961 bytes --]