Community
Participate
Working Groups
In recent versions of eclipse your project will export to "./projectName" in the zip archive export, yet will now only allow imports to "./projectName" placing your imported zip into "./projectName/projectName" making it impossible to directly import a project that has been exported with eclipse. This is only a recent problem as previous versions of eclipse allowed imports to "./"
You can re-import using the import projects wizard. Bug 157198 discusses how we should bring these more in line.
I think you missed the point; in previous versions of Eclipse this was possible. The only reason why it is not possible any more is because the validation check got changed to not allow imports to "./". In short the archive export is 100% incompatible with the archive import, i.e. if you export an archive you cannot import the said archive directly back into Eclipse like you were previously able to.(In reply to comment #1) > You can re-import using the import projects wizard. > > Bug 157198 discusses how we should bring these more in line. >
I'm not sure why this was removed as I was not the developer on import at the time. Karice was this intentional?
Well (although it is not my question) in all honesty I think that the decision to remove "./" was a good one as it (the import method) only works when the directory structure of the archive corresponds with the project name (including case). It appears (in my opinion) that the corresponding change in the archive export was simply missed out </theory>. The use of the archive import/export feature appears to have been initially designed for importing and exporting the entire workspace and not for this type of usage (management of single projects) which is reflected in its functionality. Of course I am basing this all on the appearance of the features, but it does look like the area will eventually be resolved. (In reply to comment #3) > I'm not sure why this was removed as I was not the developer on import at the > time. Karice was this intentional? >
I don't recall if this was done intentionally (I can't imagine it was). Keldon says a validation check was changed. Has anyone looked into the details of that?
"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.
