score:177

Accepted answer

this happened to me. i'm still not sure how, but the reason was that my workspace meta data had become corrupted, probably due to eclipse being improperly shutdown. the solution, as explained here, is to:

note, steps 2 & 3 are optional if eclipse isn't crashing, but just not showing any projects.

  1. close eclipse.
  2. cd /home/user/workspace/.metadata/.plugins
  3. mv org.eclipse.core.resources org.eclipse.core.resources_bak
  4. start eclipse
  5. do file->import
  6. general->existing projects into workspace
  7. click the "select root directory" field and browse to each subfolder in your workspace folder, and import.

for me, this was very tedious, since i had several dozen projects in my workspace, but it's the only solution i found short of restoring my entire workspace from a backup.

edit: this answer is now quite old, and better solutions may now exist. although i haven't had need to try it, i recommend attempting @antonagestam's solution first, as others have suggested it may be faster and more effective.

edit: since it's fairly simple, i'd recommend trying antonagestam's solution first. however, this problem recently re-occurred for me, and that solution did not work in my case. but neither did it interfere with this solution.

score:-1

i tried differently for the same issue and worked .

go to your project location in hard drive. ex: /home/user/workspace/project/settings and delete this file org.eclipse.core.resources.prefs

for full details check out bellow link

http://errorkode.com/viewtopic.php?f=20&t=8&sid=40cff1661bf0ace12878d6d6fb7e75ac

score:0

solution that cerin provide, importing each time that this problem happens, could be boring.

so i've implemented a script that control if workspace setting exits: if not, restore it to default.

i have an eclipse shortcut icon on the top panel that execute:

 /opt/eclipse/checkworkspace && /opt/eclipse/eclipse

script checkworkspace is the seguent:

#!/bin/bash

eclipse_config_path="/opt/eclipse/configuration"
eclipse_config_file="config.ini"
eclipse_config_setting="osgi.instance.area.default"
default_workspace_path="@user.home/workspace"
eclipse_log="/var/log/eclipse.log"

cd ${eclipse_config_path}

function sedeasy {
  sed -i "s/$(echo $1 | sed -e 's/\([[\/.*]\|\]\)/\\&/g')/$(echo $2 | sed -e 's/[\/&]/\\&/g')/g" $3
}

workspace_exists=$(cat ${eclipse_config_file} | grep ${eclipse_config_setting})

# if workspace setting doesn't exists 
if [ -z "$workspace_exists" ]; then
  echo "worskspace setting not exists, resetting to default." >> ${eclipse_log}
  newconf=${eclipse_config_setting}"="${default_workspace_path}
  echo ${newconf} >> ${eclipse_config_file}     
else    
   # if setting exist but it is empty
   vals=(${workspace_exists//=/ }) 
   length=$(echo ${#vals[@]})
   if [ "${length}" -lt 2 ]; then
       newconf=${eclipse_config_setting}"="${default_workspace_path}
       conftoreplace=$(echo ${vals[0]})
       sedeasy ${conftoreplace} ${newconf} ${eclipse_config_file}
       echo "worskspace exists but is empty, resetting to default." >> ${eclipse_log}
   else
      echo "worskspace already set:" "${vals[1]}"
   fi
fi

maybe could be semplified, but works.

score:0

i tried many solutions. i found mine in the drop down menu of the entreprise explorer: - deleting org.eclipse.core.resources has no effect. - "top level elements -> projects" was already checked for me; swtiching with documents has no effect. - selecting all extensions in the filter option of the drop down menu has no effect at first sight, maybe it solve part of the problem.

the solution come from "unselecting documents" (third choice in the entreprise explorer drop down menu). i think that choice reset the filtering of documents displayed in the explorer.

hope it'll helps jn gerbaux

score:0

tedious but it worked for me (kepler):

  1. using the os zip utility, zip everything below the project workspace folder to a zip file, to be placed in a separate directory (will use c:\tmp\workspace.zip as an example).

  2. unzip workspace.zip to the c:\tmp directory. assume there's a project folder called project1

    a. ensure all the files in project1 have full control permissions for everyone or at least 777 permissions.

  3. remove all the project folders in the eclipse workspace.

  4. recreate each project one by one according to its original type (java, dynamic web, etc.). (will use project1 as an example.) do not add anything.

  5. in eclipse, do file -> import -> file system. then select c:\tmp\project1 as a source

  6. select the workspace project1 as a destination. do not overwrite any file.

  7. in eclipse, refresh the project and test it. it should work.

score:0

also had this problem.

my solution was to uncheck the box pydev: closed projects, even if those hidden projects are php and not python projects. (strange bug in eclipse/aptana???)

be aware that even "closed projects" (a topic above pydev closed projects) is also unchecked. so you have to uncheck both settings.

this: eclipse shows only "open projects" in project explorer

score:0

all of my projects were closed and i had hid the closed projects in the settings. so to open projects go to top right view menu, and uncheck closed projects option. assuming it is checked already.

enter image description here

score:0

do the following steps

         file --> import --> existing projects into workspace

         select the root directory as ur old root folder

         finish.

yahoo.. there is ur old projects again in ur project explorer

score:0

1) file > import > existing projects into workspace 2) choose your workspace folder 3) select all of your projects 4) finish

all are ok with above way !!!

score:0

file - import - existing projects into workspace - browse - choose your workspase - done!

score:0

if eclipse was killed during a shutdown, the projects database may become corrupted (the project database is normally located in: workspace/.metadata/org.eclipse.core.resources/.root/1.tree).

a message like this will be logged in workspace/.metadata/.log:

!message could not read metadata for '.../.metadata/.plugins/org.eclipse.core.resources/.root/.markers'.

the data is lost. you need to import your projects again (file->import -> general->existing projects into workspace).

the list of projects that were in the workspace can still be seen in .metadata/org.eclipse.core.resources/.projects/.

projects located outside the workspace will have a .location file with the path to the project.

score:0

i also had the same problem.

file>restart. projects and modules appeared after restarting the eclipse, but faced new error; an internal error occurred during: "appxray indexing...". java.lang.nullpointerexception.

so it's good to be on safe side, import the project again in a new workspace.

score:0

if you go to quick access and type in projects you will get it your projects back.

score:0

choose
file > switch workspace> 'myworkspace'

eclipse restarts and if you are as lucky as me, the projects are mapped correctly.


in my case i have the developer environment on a shared server with about 10-15 users that may accidentally change things that affects other users.

tip of the day: don't do that...

score:0

i had this trouble recently, but in my case i hid all items by myself when check all items in "filters and —Āustomization" dialog.

i just didn't read note on top of them, and had thought that checks will allow to see any additional items in project explorer. but in reality, checking that checks hide corresponding items from explorer!

please note this! )

dialog:

dialog

way to open this dialog:

way to open this dialog

score:0

as a preliminary (before reimporting everything), here is a solution to recover working sets in which project were (if any).

i had more than 100 projects and each was in one of 14 working sets. if your top level elements changes (accidentaly or not if it is a bug) from "working set" to "projects", you only see projects that are not in a working set, and if, as i do, you don't have any projects outside a working set, you think all is lost because you cannot see anything (blank package explorer). so the solution is now obvious: click on the top left small white triangle menu, than select "top level elements", than select "working sets". you also have the possibility to rearrange the working sets list items. hope it helps unfortunatly the working sets were empty after the recovery, but at least i recovered their names.

config: eclipse oxygen.2 release (4.7.2) with java 1.8 on windows 10.

score:1

when this happened to me i had somehow set the project explorer to only display working sets. i had none, so nothing was displayed.

to fix it, i went to the project explorer view menu (next to the minimize and maximize icons in the project explorer), top level elements -> projects.

thanks to @antonagestam for pointing me in the right direction.

score:1

it seems it happens to us all. i was happily hacking away at javascript, nowhere near all the nasty hibernate java stuff, and boom, "cant find org.jboss.logging.basicloging". i havent touched anything!. after an hour or so of trying to make that appear, restarting servers, mysql, eclipse, adding jars that weren't needed before,i deployed the fix all solution, the off button. then zap, no project. (i am still none the wiser as to why calling configuration() should now require jboss-logging...jar, maybe i needed it all along for when bad things happen)

my input is

  1. use git, keep as little of your stuff in the eclipse workspace area as possible. then just import project from existing git repo when eclipse loses it's marbles.

  2. i also lost my server config. it's there but eclipse insists there no server config stuff and bombs. so make another one, i've expressed my feelings about eclipse in my new server name, and copy your apache xml configs (workspace/servers/i_love_eclipse) over from the original perfectly good directory.

score:1

not sure how/why, but this happened to me once when i added a task to mylyn. seemed that mylyn was filtering my projects. when i deleted the task they all came back.

score:1

none of the answers provided here worked for me. my enterprise explorer was completely grey and i couldn't even import or reimport projects.

in my .metadata.log i saw this error:

assertion failed: working set with same name already registered

so i deleted these file:

.metadata.plugins\org.eclipse.ui.workbench\workingsets.xml

now i can see all my projects. i didn't have to add them back again.

score:1

i found a solution that worked better for me. under my home folder i found a workspace/.metadata folder. i copied this folder into my eclipse workspace, replacing the .metadata folder that had been there. when i started eclipse everything was back to the way i had left it - all projects present, all open files were still open, etc. just like nothing had happened! i'm using neon.

score:1

got this issue on returning to an eclipse project on a vm after leaving it untouched for maybe a couple of weeks.

i started to apply the accepted answer, but when i got to the step of renaming the folder and had exited eclipse, i saw there was an instance of eclipse still running. i realized windows had for some reason started a second instance of eclipse when i hit the taskbar button. the second instance had been unable to access the workspace while the first instance was using it.

once i undid my folder rename, and closed and restarted the original instance of eclipse, i was able to use file->switch workspace to get my normal workspace back.

score:2

if you use the "task list" view of eclipse, it will sometimes try to hide files or projects that it thinks are not associated with a given task (i.e. any file that was not opened while you had a certain task selected as the current task). if you want eclipse to stop hiding files in that case, you can just delete all tasks.

or you may also restart your eclipse and by just closing the project and then opening it again (from the right mouse click context menu) the files will be restored.

if that doesnt get your projects back then check the "filters option" (click on right corner of project explorer tab and open context menu. select filters option from menu) and make sure that your projects type isnt checked.

score:2

you should check the active working set - make sure it is off.

score:3

mona is correct - make sure that you have the task list set to show all as the image shows. click the arrow to the left of the project if you want to re-factor your filter. reset your perspective if you do not see the task list.

show all projects in eclipse

score:3

if any of the previous methods don't work for you then delete your old workspace, create a new workspace and put it by default. you can do this by launching eclipse twice - the second time it asks you for the workspace ;). then re-import all your projects there and say "problem, goodbye".

score:3

today 22-03-2016, i check again this question and using eclipse mars i solved with:

  • having eclipse opened, go on file -> restart

go on same workspace and i have all project on "project explorer"

sometime also this operation, will solve (clicking on projects dor see all project!!)

 my problem

so other solution is:

solution

score:4

my solution is open view menu and select "top level elements" and set "projects"

score:13

click on windows > open perspectives > java , press ok. project explore will come back on screen..

score:13

i had the same problem in luna,

suddenly my projects were gone in start-up.
i solved this by select deselect working set option in the drop-down menu in project explorer.

note: i post this answer even this is not a right answer for this question. since i search for luna and came here,while trying with discussed things i was find this solution. this may help others.

score:15

i was having the same problem for android projects in eclipse. this link was very helpful in restoring the missing projects.

  1. go to 'file->import->general->from existing project'.
  2. select the root folder to the workspace.
  3. click on the 'refresh' button.
  4. select the required projects and click 'finish' button.

score:32

go to

file --> import --> general --> existing project into workspace

then, in root directory enter the workspace path where all your projects saved & click refresh as below

enter image description here

and click finish

enter image description here

score:83

i had the same problem in aptana, all of a sudden my projects were gone. solved it by going to the drop-down menu in project explorer and going top level elements -> projects.


Related Query

More Query from same tag