Accepted answer

i am no expert, but i just added new sites to my "available software sites" (help -> install new software -> available software sites)

and updated (help -> install updates).

after the update had been added had been disabled had been disabled

maybe other changes that i didn't notice.

everything seems to work as expected - project list remains - perspectives remain - the only thing that wasn't preserved seemed to be the editor tabs that were open in the workspace, but that is small loss. so hopefully that was the right way to do it - unless someone wants to tell me differently.



the first and second answers didn't work for me.

i ended up downloading the most recent version of eclipse and import the workspace and configurations from the previous version.

i found this video helpful


you can import existing projects from a common root folder using

file > import... > general > existing projects into workspace

in addition to the preference transfer (as thsoft suggested):

file > export... > general > preferences > export all
file > import... > general > preferences > import all


you can use eclipse-perspective-share to migrate your perspectives.

my 2 cents.


you can transfer most of your preferences by export... > preferences > export all in your old installation and importing them into your new one.


edit: this is for linux users

this link should help:

essentially you just need to replace your /usr/lib/eclipse with a new download of the latest version, and that's really about it.


@alanb, that doesn't work for me, because the releases repo does not include the eclipse sdk. maybe the organization has changed since you upgraded.

i had to add the following repository: to the available software sites.

even then check updates doesn't work. have to go through the install new software path, select the above repo, and then it shows eclipse sdk, eclipse platform sdk, etc. options. have to select the correct option to upgrade depending on the current installation (i.e., if it was a platform or sdk, etc.)

hope this helps someone.



you guys are making this into a much bigger issue than it really is, eclipse is designed to be portable, i.e. it doesn't need to be installed or store settings in the registry etc...

upgrading and maintaining settings is as simple as downloading version y and extracting it into the version x folder overwriting everything but the configuration folder. the new version configuration folder only has 2 or 3 generic files in it anyway until after the first time it is run. i've done this over the past 4 versions of eclipse and never had a problem.

the only thing to keep in mind is that anything that's not included in whichever specialized version you're using may need to be upgraded, but that's simply a matter of clicking check for upgrades under help after running the new version for the first time.


i followed the same way that alanb described and had no problems upgrading from indigo:

  1. add the juno update site and the update sites of other projects you are using (under eclipse > preferences > available software sites)

  2. select help > check for updates

  3. follow the update wizard (select everything you need, accept everything you have to)

  4. restart eclipse

additional information:

faq entry in the wiki: "how do i upgrade eclipse?"

eclipse juno (4.2) readme (slightly more detailed): "upgrading workspace from a previous release"

Related Query

More Query from same tag