Eclipse starts from scratch

[firefexx]

Hi, after I upgraded Fedora 15 to 16, I installed openjdk7 and configured Eclipse 3.7 to use the new Java version.
Then I removed my old workspace and the ~/.eclipse folder because I wanted a fresh Eclipse without old setting from 3.6.

The problem is, I got that fresh Eclipse each times I launch the application! oO
I can choose a new Workspace and it creates a new ~/.eclipse folder for settings, but it seems that Eclipse forgets this settings when I start it again.
Then I have to choose a new workspace, say that Subclipse should not send usage data, close the welcome perspective and configure the stuff I want. Each time!

What goes wrong? Is it a Eclipse or a Fedora problem and does someone know what I can do now? It's really annoying.

Thanks
Bye

[weitjong]

I had exactly this problem a few days ago but it is fixed after one of the yum update upgraded a few eclipse-* packages in my system. My eclipse-platform has version 3.7.1 now and I am using the Fedora stocked IcedTea6.

[firefexx]

Hi, thanks for your reply.

My system is up-to-date too, but the problem is still present.

(I have to correct my statement above that I have to choose the workspace each startup. Eclipse creates the default workspace in ~/workspace without asking me..)

Maybe it depends on Java 7?! You use 6?

[weitjong]

Originally Posted by firefexx

(I have to correct my statement above that I have to choose the workspace each startup. Eclipse creates the default workspace in ~/workspace without asking me..)

Maybe it depends on Java 7?! You use 6?

I know exactly what you are saying. Believe me, I do. I have a few workspaces for different purposes. All the workspaces are resided in "~/workspaces" folder (note the plural form). Before the problem was fixed, eclipse ignored my setting to allow me to "choose workspace" upon start and always tried to recreate the default "~/workspace" with the fresh setting (including answering the stupid subversion prompt again and again). It was a pain the a**. Fortunately, this madness stops after the package update. I am not sure why it does not work for you though but have you double checked your Eclipse preference on the "Prompt for workspace on startup" setting?

I can confirm I use 6. This is the configuration setting from Eclipse Help/About.

-showsplash
-launcher
/usr/lib64/eclipse/eclipse
-name
Eclipse
--launcher.library
/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1. 100.v20110505/eclipse_1407.so
-startup
/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.overrideVmargs
-exitdata
8001
-vm
/usr/bin/java

And below shows the java version.

$ /usr/bin/java -version
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.4) (fedora-61.1.10.4.fc16-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

[firefexx]

Hmm, same configuration but other Java version.

$ /usr/bin/java -version
java version "1.7.0_b147-icedtea"
OpenJDK Runtime Environment (fedora-2.0.3.fc16-x86_64)
OpenJDK 64-Bit Server VM (build 21.0-b17, mixed mode)

Yes I checked the option that Eclipse should remember the workspace location.

... no idea what I can do ...

[weitjong]

It is a bit of a long shot. Are you also using eclipse-cdt? Currently I use eclipse mainly as C/C++ IDE. My system has the latest eclipse-* packages, except the eclipse-cdt package. I have installed 'eclipse-cdt' from the "testing" repo.

If you are not using CDT then just ignore this post. Hopefully others may be able to help to shed some light.

[firefexx]

Oh...
It seems that `yum update eclipse-cdt --enablerepo=updates-testing` solves the problem. oO
I have to test it one or two days to ensure that but actually it works

Thanks a lot!


By the way, I have another question concerning Java7.
I had to manually change from Java 6 to 7, so I had to specify the path to Java 7 JRE in the Eclipse settings.
The Problem is, there are a lot of similar folders and I don't know which is the best to choose in Eclipse.

$ ls /usr/lib/jvm
java                               jre
java-1.5.0-gcj-1.5.0.0             jre-1.5.0
java-1.6.0                         jre-1.5.0-gcj
java-1.6.0-openjdk-1.6.0.0.x86_64  jre-1.6.0
java-1.6.0-openjdk.x86_64          jre-1.6.0-openjdk.x86_64
java-1.7.0                         jre-1.7.0
java-1.7.0-openjdk-1.7.0.1.x86_64  jre-1.7.0-openjdk.x86_64
java-1.7.0-openjdk.x86_64          jre-gcj
java-openjdk                       jre-openjdk

Bye

[weitjong]

Glad to hear that.

As for your next question. Have you looked at how the "alternatives" work? In my system "alternatives" uses the "auto" setting, meaning it automatically points to the 'best' version available. This is what I have.

$ ls -l /usr/bin/java
lrwxrwxrwx. 1 root root 22 Dec 18 10:49 /usr/bin/java -> /etc/alternatives/java

$ ls -l /etc/alternatives/java
lrwxrwxrwx. 1 root root 46 Dec 18 10:49 /etc/alternatives/java -> /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java

To check the alternative setting:

$ alternatives --display java
java - status is auto.
 link currently points to /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java
/usr/lib/jvm/jre-1.5.0-gcj/bin/java - priority 1500
 slave keytool: /usr/lib/jvm/jre-1.5.0-gcj/bin/keytool
 slave orbd: (null)
 slave pack200: (null)
 slave rmid: (null)
 slave rmiregistry: /usr/lib/jvm/jre-1.5.0-gcj/bin/rmiregistry
 slave servertool: (null)
 slave tnameserv: (null)
 slave unpack200: (null)
 slave jre_exports: /usr/lib/jvm-exports/jre-1.5.0-gcj
 slave jre: /usr/lib/jvm/jre-1.5.0-gcj
 slave java.1.gz: (null)
 slave keytool.1.gz: (null)
 slave orbd.1.gz: (null)
 slave pack200.1.gz: (null)
 slave rmid.1.gz: (null)
 slave rmiregistry.1.gz: (null)
 slave servertool.1.gz: (null)
 slave tnameserv.1.gz: (null)
 slave unpack200.1.gz: (null)
/usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java - priority 16000
 slave keytool: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/keytool
 slave orbd: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/orbd
 slave pack200: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/pack200
 slave rmid: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/rmid
 slave rmiregistry: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/rmiregistry
 slave servertool: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/servertool
 slave tnameserv: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/tnameserv
 slave unpack200: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/unpack200
 slave jre_exports: /usr/lib/jvm-exports/jre-1.6.0-openjdk.x86_64
 slave jre: /usr/lib/jvm/jre-1.6.0-openjdk.x86_64
 slave java.1.gz: /usr/share/man/man1/java-java-1.6.0-openjdk.1.gz
 slave keytool.1.gz: /usr/share/man/man1/keytool-java-1.6.0-openjdk.1.gz
 slave orbd.1.gz: /usr/share/man/man1/orbd-java-1.6.0-openjdk.1.gz
 slave pack200.1.gz: /usr/share/man/man1/pack200-java-1.6.0-openjdk.1.gz
 slave rmid.1.gz: /usr/share/man/man1/rmid-java-1.6.0-openjdk.1.gz
 slave rmiregistry.1.gz: /usr/share/man/man1/rmiregistry-java-1.6.0-openjdk.1.gz
 slave servertool.1.gz: /usr/share/man/man1/servertool-java-1.6.0-openjdk.1.gz
 slave tnameserv.1.gz: /usr/share/man/man1/tnameserv-java-1.6.0-openjdk.1.gz
 slave unpack200.1.gz: /usr/share/man/man1/unpack200-java-1.6.0-openjdk.1.gz
Current `best' version is /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java.

HTH.

[firefexx]

Ok, thanks again