Import existing projects into my workspace [message #28854] |
Thu, 24 February 2005 20:01  |
Eclipse User |
|
|
|
Originally posted by: leeadavisAtYahoo.com.nospam.com
I want to get an existing project into my workspace. ( E.g.
http://ical4j.sourceforge.net ).
So I naturally thought there was a way to do that with file import. But
Eclipse has a paridigm I do not understand; i.e. the importing of the
project does not copy the project to my workspace. Via google, I have
found others with that problem and they eventually came up with the
solution to
1)copy existing project under their workspace directory and then
2) import existing project from that directory to "activate" the project
as part of the eclipse workspace.
1) So I downloaded and unzipped ical4j and have on my e: drive what
appears to be a complete directory structure including a .project file.
If i try to import existing project from here, it does not copy the files
to my workspace.
2) So I copy that directory to my workspace directory and then try to do a
file import existing project from that directory ( which the Googled seem
to have had success with )and it fails. I get "Invalid project
description". The details button shows
"C:/EclipseWorkspace/ical4j-0.9.11 and C:/EclipseWorkspace overlap."
where C:/EclipseWorkspace is my workspace.
I am obviously missing some concept since I am unable to get existing
projects in. I had previously tried to import an Ant project ( Apache
common libs ) and the Ant import similarly failed to copy the files to
the workspace where they need to be.
TIA,
Lee
|
|
|
|
Re: Import existing projects into my workspace [message #29636 is a reply to message #28854] |
Fri, 25 February 2005 12:30  |
Eclipse User |
|
|
|
Originally posted by: ian.no.spam.please
Lee Davis wrote:
> I want to get an existing project into my workspace. ( E.g.
> http://ical4j.sourceforge.net ).
>
> So I naturally thought there was a way to do that with file import. But
> Eclipse has a paridigm I do not understand; i.e. the importing of the
> project does not copy the project to my workspace.
That is the intended behaviour; it tells you this in the Import dialog,
as soon as you select "Existing Project into Workspace" (read the top
line). But this doesn't really matter where the files are, as long as
there is a Project created (parts of which are hidden, alas, in ugly
binary files in the .metadata directory), then Eclipse is
able to work with the project nicely. I just did this for ical4j and
Eclipse is happy with the project file (so we know that its .project
file is not corrupted, as another poster suggested).
If you really want the project physically stored in your workspace, one
way to do so is to check it out via anonymous CVS (I presume ical4j
supports this; I think all SourceForge projects do). Either use Import->
Checkout Project from CVS or open the CVS Locations view.
|
|
|
Powered by
FUDForum. Page generated in 0.08798 seconds