unable to access jaunty eclipse projects

Asked by N7DR

Binary package hint: eclipse

I have a project that I was working on with eclipse under jaunty kubuntu.

Now that I've "upgraded" to karmic, I can't find any way to access the project. The "Open Project" menu option is greyed out; the import feature doesn't seem to do anything useful [and I'm not even sure that "import" is the right thing to do anyway].

No doubt there is a way to access the project, but it is horribly, horribly non-obvious what this way might be.

(Naïvely, I expected that the project would simply open in the new version of eclipse, à la MS Dev Studio; since karmic's eclipse doesn't do that, users need clear instructions as to how to get to their old projects.)

ProblemType: Bug
Architecture: amd64
Date: Tue Nov 10 14:16:21 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: vmnet vmci vmmon fglrx
Package: eclipse (not installed)
 PATH=(custom, user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: eclipse
Uname: Linux 2.6.31-14-generic x86_64

Question information

English Edit question
Ubuntu eclipse Edit question
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #480291.

Revision history for this message
N7DR (doc-evans) said :
Revision history for this message
Rockwalrus (rockwalrus) said :

If you open the same workspace location as your previous eclipse install, the projects should just open. But if they do not, use "Import...->Existing Projects Into Workspace" to open up your old projects. You will need to find their location on the filesystem in order to import them.

Revision history for this message
N7DR (doc-evans) said :

I have no doubt at all that, as you say, "the projects should just open". That's exactly what I expected.

I filed this as a bug for the simple reason that this is not what happens. I spent pretty much a whole day on this, trying everything I could think of, and the closest I ever got was to have an infinite recursion of directories created. I have now switched to Dev Studio on Windows for this project, because I have to have a working development environment and I could waste no more time trying to fix something that was broken by the switch from jaunty to karmic :-(

Sorry, but sometimes the need to be productive trumps one's desire to use an open source tool.

Can you help with this problem?

Provide an answer of your own, or ask N7DR for more information if necessary.

To post a message you must log in.