Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Proposal for refresh behavior in Project Explorer
Proposal for refresh behavior in Project Explorer [message #846681] Mon, 16 April 2012 12:59 Go to next message
David Straayer is currently offline David Straayer
Messages: 3
Registered: February 2012
Junior Member
Here is my situation: I use Eclipse on a lot of different computers, with workspaces on different local and network drives. Sometimes I want to copy a project from one workspace to another. For example, to copy a file I've checked out on a local drive into a network drive to share with my students.
I can easily copy the subtree associated with the project from one workspace to another, no problem. But when I do, and open up Eclipse pointed to the workspace to which I've copied the subtree, Package Explorer doesn't "see" the files in the folder.

Someone suggested using Import/Export, but that isn't very convenient in a teaching and grading environment. I can FTP over a folder of src, but unless I run Eclipse on the other machine, I can't export. And Export is a cumbersome set of other operations that I usually use for building runnable jar files, so using it for this purpose causes it to "forget" my current jar build configuration.

I don't understand why right-clicking on a src folder or package icon, and clicking or "refresh" or stabbing F5 doesn't cause Eclipse to read the files in the folder, and create or delete items in the Package Explorer appropriately. My students are often downloading demo source code from my workspace, which I keep in a searchable directory on my web space. But they've got to go through extra steps to open the files in Eclipse. Creating a new class with the identical name to a file already in the directory seems to work, but that is cumbersome and error-prone.

Why not add a checkbox somewhere in preferences that says something like "Make F5 refresh src and package icons in Package Explorer.", default it to the current behavior (for whatever reason nobody seems to want F5 to refresh Package Explorer. I don't understand, but, hey, you've probably got a reason). That way, everybody who likes it the way it is now keeps it the way it is. And those of us who are teaching the way I am can get demo code into Package Explorer for ourselves (for grading) and for our students (for demo and trial modification in class).
Re: Proposal for refresh behavior in Project Explorer [message #855067 is a reply to message #846681] Tue, 24 April 2012 09:49 Go to previous message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

Copying the subtree from one workspace's folder to another puts them out of sync, but I don't understand what you mean about F5.

If I copy my src directory to the src in another workspace's project src, I can select the project and hit F5 and the package explorer updates correctly. Is that not what you are seeing?

PW


Previous Topic:How to get rid of unwanted menu contributions registered against MenuUtil.ANY_POPUP
Next Topic:Hiding a ViewPart instead of closing
Goto Forum:
  


Current Time: Mon Sep 01 09:57:54 EDT 2014

Powered by FUDForum. Page generated in 0.01512 seconds