** Changed in: eclipse (Debian)
Status: Fix Committed = Fix Released
--
[Reopened] [Dapper] Eclipse startup script should respect jwm setting via
update-alternatives
https://bugs.launchpad.net/bugs/36534
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: eclipse (Debian)
Status: New = Fix Committed
--
[Reopened] [Dapper] Eclipse startup script should respect jwm setting via
update-alternatives
https://bugs.launchpad.net/bugs/36534
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
There are no longer any special hacks from our side that chooses the
JVM.
~Niels
** Changed in: eclipse (Ubuntu)
Status: In Progress = Fix Released
--
[Reopened] [Dapper] Eclipse startup script should respect jwm setting via
update-alternatives
https://bugs.launchpad.net/bugs/36534
We will try to fix this in eclipse 3.5.0-1
~Niels
** Changed in: eclipse (Ubuntu)
Status: Confirmed = In Progress
** Changed in: eclipse (Ubuntu)
Assignee: MOTU Java Growers (motujava) = Niels Thykier (niels-thykier)
--
[Reopened] [Dapper] Eclipse startup script should respect
Well, I had the same error (the vm ) after upgrading ubuntu 8 to 9.
I'd installed java-6-sun-1.6.0.13 but after the update my $JAVA_HOME pointed to
java-6-sun-1.6.0.10.
Crap! Short discussion with my environment settings does not solve the problem.
:-(
Checking out /usr/bin/java I saw that
hi,
here is an offtopic question :
About your script, is there a policy to setup jvm per applications ?
For tuxguitar package I had to write a script that guess best installed jvm,
but i am not very proud of it ...
Regards
--
[Reopened] [Dapper] Eclipse startup script should respect jwm
The sanest fix should be to have /etc/eclipse/java_home have
/usr/lib/jvm/default-java as the first line.
--
[Reopened] [Dapper] Eclipse startup script should respect jwm setting via
update-alternatives
https://bugs.launchpad.net/bugs/36534
You received this bug notification because you are a
On October 28, 2008 04:09:59 George Pollard wrote:
The sanest fix should be to have /etc/eclipse/java_home have
/usr/lib/jvm/default-java as the first line.
Not very useful if you don't have such a file! The point of using
update-alternatives is that this is the way that java (and other)
** Bug watch added: Debian Bug tracker #353360
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=353360
** Also affects: eclipse (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=353360
Importance: Unknown
Status: Unknown
--
[Reopened] [Dapper] Eclipse startup script
** Changed in: eclipse (Debian)
Status: Unknown = New
--
[Reopened] [Dapper] Eclipse startup script should respect jwm setting via
update-alternatives
https://bugs.launchpad.net/bugs/36534
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
i'm also stuck on this.
- installed java-5
- installed eclipse
- eclipse ran fine
- installed java-6
- uninstalled java-5
- eclipse from the menu gives: The custom VM you have chosen is not a valid
executable.
- uninstalled completely/reinstalled eclipse
- same problem
eclipse from the command
I agree with Erich ( Dennis - I'm not sure why you retracted your
comment!)
update-alternatives (and update-alternatives-java) are the _proper_ way
to set your default VM. eclipse should be respecting that.
I agree that update-alternatives is not able to handle JAVA_HOME is an
unconvincing
This bug is already present in windows too, eclipse 3.0 version goes
along with java 1.4.x and below versions, i think its the problem with
the eclipse package,
--
[Reopened] [Dapper] Eclipse startup script should respect jwm setting via
update-alternatives
https://bugs.launchpad.net/bugs/36534
13 matches
Mail list logo
