Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321073

Summary: Working sets refresh problem
Product: [Technology] DLTK Reporter: Janos Haber <boci.boci>
Component: RubyAssignee: dltk.ruby-inbox <dltk.ruby-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: boci.boci, os-dev
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Janos Haber CLA 2010-07-27 18:34:09 EDT
I using latest DLTK - Ruby. If I set working sets to top level elements (in script explorer), the ruby projects will go crazy (If I create second level folder it's contains same folder twice (source and normal folder icon). If I  move a folder or delete it's not refreshed (f5 or refresh not working). If I switch back to normal top level it's work fine...

b0c1
-- Configuration Details --
Product: Eclipse Platform 3.6.0.v201006080911 (org.eclipse.platform.ide)
Installed Features:
 org.eclipse.platform 3.6.0.v20100602-9gF78GpqFt6trOGhL60z0oEx3fz-JKNwxPY
Comment 1 Jason Craig CLA 2010-07-29 20:15:37 EDT
The component on this should probably be "common" I imagine--it is affecting the script explorer for Python projects as well.  Also the importance should be "minor" or "normal", this is a new bug in 2.0.

I'm running Linux x86_64, Eclipse Helios (3.6.0), DLTK Core 2.0.0 and DLTK Python 2.0.0.  Any resource created or deleted in a Python project will not be shown in (or removed from) the Script Explorer unless Eclipse is restarted or the project is closed and opened again.  As Janos Haber stated, this only applies when "Top Level Elements" is set to "Working Sets".  Everything seems to work fine when it is set to "Projects".
Comment 2 Dawid Pakula CLA 2020-01-03 07:58:49 EST
Ruby support has been removed.