Community
Participate
Working Groups
I try to import an existing project into a workspace: The workspace is in c:\eclipse\workspace and the project is in c:\eclipse\workspace\rmi-generate The wizard correctly identifies the directory (shows the project name), but when I hit "Finish" it displays an error message "Invalid project description". I've seen the other bug about it - but I see this behavior again and the project location is valid (directly under the workspace directory) I use Eclipse3.0M6 on WindowsXP.
The other bug is bug #33684
I see the other bug is assigned UI component, so I change it here as well.
Changing owner to match component but will investigate to see what the story is. The referenced bug was fixed in 2.1.1 so it shouldn't be a problem in the latest builds.
Is there any information in your .log file? (/workspace/.metadata/.log) What directory is Eclipse installed in?
Actually I'll move it back to Core until we can determine more information.
I debugged it a little and here are the results - It seems to happend for project which directory name is different from the project name in the .project file. The failing line is line 128 in the Project class workspace.validateProjectLocation(project, location) Genady
I am getting this too. "Invalid project description" c:/Development/Projects/CUWebAuth and c:/development/projects overlap. This results in a bogus compile error: "The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object." Most of the time Eclipse is just fine but randomly it will start doing this and nothing will build. I just specify my data directory with -data param as normal. At no time have I ever nested projects or done anything like that. Log stacktrace is: Java Model Exception: Core Exception [code 77] Invalid project description. at org.eclipse.jdt.internal.core.DeltaProcessingState$ProjectUpdateInfo.updateProjectReferencesIfNecessary(DeltaProcessingState.java:154) at org.eclipse.jdt.internal.core.DeltaProcessingState.performClasspathResourceChange(DeltaProcessingState.java:223) at org.eclipse.jdt.internal.core.SetClasspathOperation.updateProjectReferencesIfNecessary(SetClasspathOperation.java:771) at org.eclipse.jdt.internal.core.SetClasspathOperation.executeOperation(SetClasspathOperation.java:246) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:700) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673) .... Caused by: org.eclipse.core.internal.resources.ResourceException: Invalid project description. at org.eclipse.core.internal.resources.Project.checkDescription(Project.java:153) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:887) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:931) at org.eclipse.jdt.internal.core.DeltaProcessingState$ProjectUpdateInfo.updateProjectReferencesIfNecessary(DeltaProcessingState.java:151)
Aaron, please file a new bug report as I believe your problem might be a separate issue. Genady, I think I see what is going on. Don't know why I didn't see this before, sorry. Eclipse manages all files underneath your workspace. If your workspace is at c:/eclipse/workspace then you cannot create a project at c:/eclipse/workspace/rmi-generate unless its created at the "default location". Therefore, instead of doing an import, you need to create a new project and just accept the default location. It will see that there is a project description file already there and use that one and restore all your previous project data. Let me know if this doesn't solve your problem.
My problem is that sometimes I wish to reset the workspace by erasing the metadata. Is creating a new project equivalent to importing it? What happens if the project name is different from the directory name (I think it doesn't work well, but I didn't check recently). Genady
If the project is in the default content area, then you have to create a new project. (you aren't allowed to import it and you can't create a new one with a new name and the old location) If the project name is different than the directory name, that's ok if the project content area is not in the default area. For example: - workspace is in c:/eclipse/workspace - create new project MyProject - set project contents to be c:/temp/MyContents Are there problems that are causing you to reset your workspace? In theory you should be able to keep the same workspace across multiple builds. I upgrade to a new Eclipse integration build every week and I've had the same workspace for about 3 years now.
Based on comment #6 and the original comment, this bug appears to be a duplicate of bug 143757.
(In reply to comment #11) > Based on comment #6 and the original comment, this bug appears to be a > duplicate of bug 143757. Looks like it is the same bug. Nice to have it fixed.
