Bug 205550 - [Model] Package Explorer empty at boot time
Summary: [Model] Package Explorer empty at boot time
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2007-10-05 04:59 EDT by Xavier Stenuit CLA
Modified: 2019-09-06 15:38 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Stenuit CLA 2007-10-05 04:59:25 EDT
It is possible to have a package explorer showing empty contents in some occasions  (probably when deleting some projects from another workspace, or similar)

When this occurs, the "workbench.xml" contains the following :

<page ...>
...
<input factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/path/to/some/directory" type="2"/> 
</page>

--> if the path/to/some/directory is not existing, the package explorer will show empty contents.  

So far, I could not find any UI intervention that altered this xml element.

I think Eclipse should check that /path/to/some/directory exists, and if not, reverts so some defaults ("/" for example)
Comment 1 Kevin McGuire CLA 2007-10-09 10:41:03 EDT
Does this result in an error that you are seeing?  Is this a bug for a scenario you are using it with?  Or did you just happen to notice the workbench.xml and think it should be different in that case?

I don't know specifically, but perhaps one explanation for the current behaviour is that that the resource could come back (e.g. its on a network drive that happens to inaccessible at that moment).  In which case, you'd like to preserve the path so that the contents will be shown.
Comment 2 Xavier Stenuit CLA 2007-10-17 05:41:39 EDT
(In reply to comment #1)
> Does this result in an error that you are seeing?  Is this a bug for a scenario
> you are using it with?  Or did you just happen to notice the workbench.xml and
> think it should be different in that case?
> 
> I don't know specifically, but perhaps one explanation for the current
> behaviour is that that the resource could come back (e.g. its on a network
> drive that happens to inaccessible at that moment).  In which case, you'd like
> to preserve the path so that the contents will be shown.
> 

It occured on my installation, while I was developing - unfortunately, I can not figure out what sequence of operation left the configuration file in this state.

Each time I restarted Eclipse, an empty package manager was shown - annoying.

I discovered the existence of workbench.xml later, when trying to fix this issue.
Comment 3 Marko Schulz CLA 2008-01-07 06:44:03 EST
We experienced the same problem. This was triggered by changes we did externally to the project directories. 

Someone changed the layout of our subversion repositories and we updated the files on our hard drives with an external SVN-Client (TortoiseSVN). With this update some projects were removed - particularly one called foo_general. After this one of our developers restarted eclipse and experienced the phenomenon described in this bug.

Below the package explorer's title bar was foo_general, the name of a deleted project on a gray background, just like it was selected via "Go into" in the context menu. The buttons "Up to workspace" and "Back to workspace" in the package explorers title menu were inactive. There was no entry in the error log.

The developer couldn't remember whether she has stepped into the project foo_general with "Go into" prior to the deletion of the project.

After finding this bug report I manually replaced all occurrences of /foo_general in the file workbench.xml with / and the package explorer was back to normal.
Comment 4 Susan McCourt CLA 2009-07-09 19:20:12 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:38:10 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.