The current eclipse no longer uses this method to determine which JVM to
use, see LP #36534.
~Niels
** Changed in: eclipse (Ubuntu)
Status: In Progress => Invalid
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://bugs.launchpad.net/bugs/45347
You received thi
> Why hasn't this patch been committed yet?
I can name two possible reasons:
* The patch is against an installed system rather than the build system
* It is more "correct" to fix 36534 [1] if possible.
We will try to fix 36534 [1] in 3.5.0-1 and there by closing this. If
fixing 36534 turns out
Why hasn't this patch been committed yet?
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://bugs.launchpad.net/bugs/45347
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs
If "/usr/" always works for update-alternatives surely the simplest fix
is to truncate /etc/jvm and /etc/eclipse/java_home to just the line
"/usr" (or /usr/lib/jvm/default-java)?
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://bugs.launchpad.net/bugs/45347
You receiv
Can this please be fixed in Interpid Ibex? The bug is growing a bit of a
beard and such a basic thing should be taken care of very well.
For beginner and intermediate programmers it is demotivating when having
to double check several different configuration settings and installed
packages before E
i am a newbie
can you tell me how to save a patch?
where to save a patch?
the usr/bin/eclipse is not a folder, and even it is, its locked, i can't
save anything on it!
i couldn't run the command
sudo patch eclipse_launcher_should_use_global_java_conf.patch
it says:
sudo: patch: command not foun
Situation on Hardy Heron is not much better. After standard installation, one
has to install:
1) eclipse
2) sun-java6 (and friends)
But this lead to a configuration on your system that is polluted with gij and
gic settings.
One has to manually set:
a) alternatives to sun-java6
b) edit eclipse co
Still here, any news on this?
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://bugs.launchpad.net/bugs/45347
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I run this command:
$ sudo ./update-java-alternatives -s java-6-sun
but had to do this manually:
$ sudo vi /etc/jvm (and add the following line to the top of the list)
/usr/lib/jvm/java-6-sun
$ sudo vi /ect/eclipse/java_home (and add the following line to the top of the
list)
/usr/lib/jvm/java
If the /usr results in "alternatives" being used, I'm happy with that -
it wasn't obvious, because of course that was never present in
/etc/eclipse/java_home. I'll remove my manually added link to sun-
java-6 and try it.
The second point about Debian packages not being permitted to rely on
enviro
On Thu, 2007-07-12 at 16:41 +, auspex wrote:
> I'm not asking for an "alternative" to be applied to a specific
> application, I'm suggesting that Eclipse should take advantage of that
> system-wide setting. That's quite a difference. In any case, /etc/jvm
> is ALSO system-wide, so where's the
I'm not asking for an "alternative" to be applied to a specific
application, I'm suggesting that Eclipse should take advantage of that
system-wide setting. That's quite a difference. In any case, /etc/jvm
is ALSO system-wide, so where's the difference? The /etc/jvm file
suggests that every VM sho
Alternatives are system wide. Alternatives also cannot be applied to
specific applications. Hence the creation of the existing java-common
and eclipse methods.
Given that we live in a world with multiple JVMs, some of which work
better than others for different purposes, when coming up with these
I opened bug #125274 about this, and it got marked a duplicate, but I'd
beg to differ (slightly).
imo, neither the java-common nor eclipse methods are correct.
We have an "alternatives" system, which should always be configured with
the user's preferred VM. Alternatives should be used rather tha
** Tags added: packaging
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://bugs.launchpad.net/bugs/45347
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Jerry:
Any chance of this getting done in time for Feisty?
** Tags added: patch
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://launchpad.net/bugs/45347
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for this. I invented this method for Eclipse, then decided the
method was pretty good, and so wrote it in java-common... but never went
back and updated Eclipse to use it. I'll clear this up sometime soon.
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://launch
The patch provided by R. A. Rivas Diaz should be applied because of the
reasons put forward: duplication of code and maintenance for the user.
** Changed in: eclipse (Ubuntu)
Status: Unconfirmed => Confirmed
--
Eclipse uses /etc/eclipse/java_home instead of java-common scripts
https://lau
18 matches
Mail list logo
