Re: not eclipserc but what?
Hi (I'm on the list),
On Sun, 15 Nov 2009 09:27:05 +0100
Niels Thykier <niels@thykier.net> wrote:
> We no longer have to search for JVMs on start up and the "Check
> for internal browser" warnings have caused nothing short of 4 bug
> reports, which displays its inability to properly detect browser support
> on a Lenny or Squeeze. It never occurred to me that other packages
> actually used this file; so I presumed we could just remove it. So...
Now eclipse uses gcj if we specify openjdk with /etc/alternatives/java
to use, unless install default-jre-headless package, but it will be fixed,
right?
> If you want to pass specific options to either eclipse or the jvm, then
> I would prefer that happened via eclipse.ini. The problem is that if
> eclipse is started with command line arguments it ignores eclipse.ini
> and users expect eclipse.ini to be parsed (because upstream's
> documentation explains how everything is done via that file). I admit it
> would better if we could get a "per user" eclipse.ini; sadly I have not
> had time to research if this is possible.
Yes, I want to pass options as VMARGS="-javaagent:/usr/lib/eclipse/plugins/
jp.sourceforge.mergedoc.pleiades/pleiades.jar -Xms40m -Xmx256m"
to use pleiades plugin which makes eclipse localized.
About pleiades, I ITPed as "Bug#555846: ITP: pleiades -- Japanese Language package for Eclipse using Dynamic AOP, Pleiades"
We can specify it as command line as eclipse -vmargs -javaagent:/usr/
lib/eclipse/plugins/jp.sourceforge.mergedoc.pleiades/pleiades.jar -Xms40m -Xmx256m
but it seems to be painful for users. If we can use eclipserc file or so,
I just ask users to copy example eclipserc file to their .eclipse directory.
You said, via eclipse.ini, it means /usr/lib/eclipse/eclipse.ini file?
Surely per-user basis setup is better, I agree.
--
Regards,
Hideki Yamane henrich @ debian.or.jp/iijmio-mail.jp
http://wiki.debian.org/HidekiYamane
Reply to: