Skip to main content

Error when opening Eclipse Application

Issue: Normally when I first install eclipse, it gives me a popup window to choose my workspace but once I select the workspace and say that it is the default one...Eclipse doesn't show that window again...This window is the "Workspace Launcher" If at all in the future I want to change the workspace I used to do so after opening eclipse and then choosing "Switch Workspace" in the File menu...This restarts eclipse and opens it again in the new workspace! It was when I got this error while opening the application.

Solution:
The default workspace is stored in the configuration\config.ini file, usually found where you installed Eclipse. If there isn't a default there (it's called osgi.instance.area) then it will prompt. If you have previously selected one, and clicked 'make this the default', then I believe it updates it in the config.ini file; if not, look in configuration\.settings\org.eclipse.ui.ide.prefs.
This files looks like this:

1--- #Sat May 31 15:23:28 GMT+05:30 2008
2--- RECENT_WORKSPACES_PROTOCOL=2
3--- MAX_RECENT_WORKSPACES=5
4--- SHOW_WORKSPACE_SELECTION_DIALOG=true
5--- eclipse.preferences.version=1RECENT_WORKSPACES=D\:\\JavaProjs

See that the 4th line gives you the option to show the workspace selection dialog box...If you want the selection everytime from now on...Just make this true else make it false

See the 5th line this will have the list of workspaces you have worked with till now...In this case it can have upto 5 entries! 5 is defined in line 3! If you want to change the workspace for this time just add or change the entry in line 5!

Save the file and reopen eclipse! It will open! Enjoy your coding!

For more information: http://www.eclipsezone.com/eclipse/forums/t78109.html

Labels:

Comments

Post a Comment

Popular posts from this blog

wget error–“zsh: parse error near &”

There is no doubt that I prefer wget way over any other type of downloads… Syntax: wget <DOWNLOAD_URL>   If you get this error “ zsh: parse error near & ” then its probably because your download URL has a “&” so you should try giving your DOWNLOAD_URL in double quotes wget “<DOWNLOAD_URL>”   If you are trying to download from a site which needs you to give your credentials then you can try giving it this way wget --http-user=<UserName> --http-password=<Password> “<DOWNLOAD_URL>”   Hope this helps
3 comments
Read more

How to Unpack a tar file on Windows?

On Windows: You can download a simple command line tool to do this. You can download the tool from here Usage can be found on the website but pasting it here too for convenience: C:\>TarTool.exe Usage : C:\>TarTool.exe sourceFile destinationDirectory C:\>TarTool.exe D:\sample.tar.gz ./ C:\>TarTool.exe sample.tgz temp C:\>TarTool.exe -x sample.tar temp TarTool 2.0 Beta supports bzip2 decompression for files with extensions like tar.bz2 and .bz2 . TarTool -xj sample.tar.bz2 temp or TarTool -j sample.bz2 Download TarTool 2.0 Beta from here Unpack a .txz file on Windows Use the 7zip tool  to unpack a .txz file on windows On Linux: You can use the bzip2 and tar combined to do this… for ex: bzip2 –cd <tar.bz_fileName> | tar –xvf - This will unpack the contents of the tar.bz file Happy Un-Tar-ing
45 comments
Read more

Ubuntu: "Unlock login keyring" message "the password you use to log in your computer no longer matches that of your login keyring"

Resetting all the keyring passwords:  Navigate to  Places > Home . Press  ctrl   h  t o view "hidden files". Navigate to  .gnome2 > keyrings and delete   login.keyring Using the same keyring (resetting keyring password but keeping old passwords in keyring): 1) Make a backup of the keyring cd ~/.local/share/keyrings/ cp login.keyring login.keyring.backup and after that delete  login.keyring  file rm ~/.local/share/keyrings/login.keyring 2) Create a new keyring file from Gnome Keyring with the name "login" 3) Replace the new keyring file with the backup of the old keyring file cd ~/.local/share/keyrings/ mv login.keyring.backup login.keyring Note: before Ubuntu 12.10 the path to the keyrings folder was   ~/.gnome2/keyrings/   instead of  ~/.local/share/keyrings/
Post a Comment
Read more