- This topic has 5 replies, 2 voices, and was last updated 20 years, 3 months ago by
.
-
Posts
-
Eclipse Version: 3.0.0
Build id: 200406251208
MyEclipse version 3.7.101
JDK:1.4.2_04
App/Web Server:Tomcat 5
OS: Win2000When I installed MyEclipse, it asked for a default project directory which I gave it the Eclipse/workspace directory. Now here’s the problem. When I put a development project underneath that workspace directory and try to import them, I’m getting a “Invalid project description” because the directory that i’m trying to import overlaps the default. I do I get around this because our development is having this same problem. Please respond ASAP.
John
Here is the actual error that i’m getting.
“Invalid project description.
C:/javadev/eclipse/workspace/GosClient/Server and C:/javadev/eclipse/workspace overlap. “John,
A few things, first the “workspace setting” when Eclipse starts up and Import/Export functionality is provided solely by Eclipse, this doesn’t come from MyEclipse. Also can you better describe what your workspace directory is set to, where the project you are trying to import is on your drive, how you are importing it, what kind of project is it and where did it come from? (copied, network mount, etc.).
Also the version of MyEclipse you gave above is not compatible with that release of Eclipse 3.0… while it might seem to work, you will likely get broken functionality and random errors. We highly suggest upgrading to MyEclipse 3.8 Beta 2 (3.7.200).
The project was copied from our repository to my harddrive so I was just locally importing from my machine. The project is a j2ee app and as my previous post states, it shows the directory problem so there is no network involved.
Actually, I’m on the beta one version. For some reason, it must have given me the wrong version, but I am on the beta one version. I also figured out a way to get around the problem. I went to switch workspace and switched it to a different directory and copied my settings over from the metadata directory. But yes, this problem NEEDS to be fixed because this error is ridulous. This has happened on prior versions that i’ve had in 2.7 and 3.0 of Eclipse. You can close the ticket.
John
Actually, I’m on the beta one version. For some reason, it must have given me the wrong version, but I am on the beta one version.
… I know you are running Beta 1, you shouldn’t be… maybe I misunderstood you but either way, you should upgrade to Beta 2 to avoid flakiness with Eclipse 3.0 final (please see previous post).
But yes, this problem NEEDS to be fixed because this error is ridulous.
I’m not sure if you read my previous post, but importing is handled by Eclipse, not MyEclipse. Unless I completely misread your message, this is what I understood you to be doing… trying to import a project from a workspace, correct?
I searched the Eclipse bug database and it seems people have some qualms with importing as well:
https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=import+project&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=3.01%2F3.1+Bugs&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=You might find someone filed a bug related to this already that you can vote on.
Thanks for getting back to me on the Eclipse error and that is good to hear that it is not apart of MyEclipse. Yes I was trying to import a project from a workspace that was already defined by a team member of mine which I had pulled off of our repository. I got around the problem by changing the workspace under the File tab. I then just copied my .metadata directory over and the setting were back to normal. It’s good to hear that other users have complained to Eclipse about the error. It’ll be fixed sooner or later.
John
