Updatesite-Access issues switching eclipse 32/64bit
Posted: Thu Aug 23, 2012 1:40 pm
After switching from eclipse 3.x 32bit to 3.x 64bit you may have problems connecting the updatesite. As reported by some users the problem even might not go away after switching to a new computer. This is most likely an incompatiblity between the eclipse 32/64 keyring binary format. Since the keyring is stored in the user home directory, switching the computer may not solve the problem if directory is located on a network device. To solve this issue you have either to delete the keyring or configure eclipse to create a new keyring at a different location.
Changing the keyring location is done by changing the eclipse.ini found in the eclipse installation directory. Add the following line somewhere above the "-vmargs" option:
After adding the eclipse.ini it should look similar like this:
To apply the changes you need close and restart eclipse.
Changing the keyring location is done by changing the eclipse.ini found in the eclipse installation directory. Add the following line somewhere above the "-vmargs" option:
- Code: Select all
-keyring
[username-home]\keyring\eclipse_32
-eclipse.keyring
[username-home]\keyring\eclipse_32\keyring
After adding the eclipse.ini it should look similar like this:
- Code: Select all
-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-keyring
x:\keyring\eclipse_32
-eclipse.keyring
x:\keyring\eclipse_32\keyring
--launcher.defaultAction
openFile
-vm
C:/Program Files (x86)/Java/jdk1.6.0_30/bin/java.exe
-vmargs
-Xms40m
-XX:MaxPermSize=256m
-Xmx1224m
To apply the changes you need close and restart eclipse.