Community
Participate
Working Groups
..at least in any way I have ever been able to discover. For example, if I pick a project "foo" in a workspace and "export to archive file". Then create a new, virgin workspace and try to import the archive file, the complaint is I cannot import until I've created a project. If I create an empty project "foo", and import the archive file, all the paths are off by one level; all the paths are foo.foo
You don't need to you choose Import > General > Existing Projects into Workspace and check "Select archive file".
Tom is probably right, "Existing Projects into Workspace" is probably what you want. I remember having similar problems, there must be something we can do to improve usability.
Changing title to reflect the described problem.
The three import wizards (File System, Archive File, Exiting Projects into Workspace) all do slightly different variations of the same thing, which is to bring something from the file system into the workspace. It seems that these three wizards can be merged into one (Import from File System) and show/hide options depending on what the user wants to import. Karice, do you know of any reasons (historical or otherwise) that required the split into three wizards in the first place? or can we just proceed with the merge?
I think because the 3 wizards are implemented so differently and because they were done at different times are the reasons why they are separate wizards. As a side note, to support EFS more we actually want these wizards to be merged (see bug 124530) but I think it may be a bit more work than it appears to be to accomplish this.
Thanks Karice. I will prototype the new merged wizard in the next little while. It is certainly going to be quite a bit of work to get it right.
One thing that I would like to point out is that in previous versions of Eclipse you were able to export and archive and then directly import it. The only reason why it does not work now is because the validation check was changed to not allow imports to "./", hence making Eclipse's archive export 100% incompatible with Eclipse's archive import. We used to transfer our project at University using archive import/export so I am no stranger to the feature. When it stopped working (in the same way) I merely extracted the archive and imported [the extracted archive]. The only reason why I noted it is because it was previously possible and now it is not after the new validation check. Having said that when the new wizard is completed this problem will be resolved so at least there is progress ^_^ Took a whole 10 months to be noticed though :)
Keldon you issue is discussed in Bug 154425 which I just reopened so we can see what the change was made for.
*** Bug 90343 has been marked as a duplicate of this bug. ***
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
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.
