| bringing existing project into new eclipse [message #77982] |
Wed, 15 June 2005 11:11  |
Eclipse User |
|
|
|
Originally posted by: adam.no.spam.cyberspaceroad.spam
I want to open up an existing Java project of src code and dirs in my
new workspace. This must be something everyone wants to do all the time.
This has puzzled me for almost a year now. I go:
- create a java project
- choose 'create from existing source'
- select the directory where the existing project is
- then I try to type a name for the project and I get this:
"cannot create project content in workspace"
and the wizard dialog won't let me go any further.
Getting around it is no great problem, just creating a new project and
then manually copying in the src and other files, but it seems I'm
missing some big concept here - there must be a reason I can't do this,
I can't believe it's a bug, so what is it?
Thanks in advance for the enlightenment!
BTW I know I can bring in my project if it's outside the workspace, but
then it's impossible to use it in CVS.
|
|
|
| Re: bringing existing project into new eclipse [message #78043 is a reply to message #77982] |
Wed, 15 June 2005 13:25  |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Which version of Eclipse are you using? In 3.01, there is no 'create from
existing source' option on the project creation wizard. Do you mean
Create Project at External Location? This is what you want to use.
Select this option, click on Browse, select the directory with your
source. As long as the directory is outside of the workspace and doesn't
create a conflict with an existing workspace, it will allow this. The
source remains in the external location. You can use CVS to manage the
source code from this location as well.
Where is your workspace in relation to the directory that contains the
existing source. They should not be in the same directory hiearchy.
Workspaces contain references to projects and configuration options you
choose. The workspace is used as the default location to create new
projects, but any major project that you are working on should not be kept
in the workspace. Leave it in the external location and let the workspace
reference this location. This will make the CVS management much easier.
Adam Hardy wrote:
> I want to open up an existing Java project of src code and dirs in my
> new workspace. This must be something everyone wants to do all the time.
> This has puzzled me for almost a year now. I go:
> - create a java project
> - choose 'create from existing source'
> - select the directory where the existing project is
> - then I try to type a name for the project and I get this:
> "cannot create project content in workspace"
> and the wizard dialog won't let me go any further.
> Getting around it is no great problem, just creating a new project and
> then manually copying in the src and other files, but it seems I'm
> missing some big concept here - there must be a reason I can't do this,
> I can't believe it's a bug, so what is it?
> Thanks in advance for the enlightenment!
> BTW I know I can bring in my project if it's outside the workspace, but
> then it's impossible to use it in CVS.
|
|
|
| Re: bringing existing project into new eclipse [message #78136 is a reply to message #78043] |
Wed, 15 June 2005 15:03 |
| Eclipse User |
|
|
|
Originally posted by: eclipse.rizzoweb.com
Dave Wegener wrote:
> Where is your workspace in relation to the directory that contains the
> existing source. They should not be in the same directory hiearchy.
> Workspaces contain references to projects and configuration options you
> choose. The workspace is used as the default location to create new
> projects, but any major project that you are working on should not be
> kept in the workspace. Leave it in the external location and let the
> workspace reference this location. This will make the CVS management
> much easier.
I have to disagree that projects should not be kept in the workspace.
Unless there is a specific reason to have the project's contents be
located elsewhere, I find it easier to have them in the workspace.
Dave, do you have a particular reason for recommending that approach?
Eric
|
|
|
| Re: bringing existing project into new eclipse [message #78194 is a reply to message #78136] |
Wed, 15 June 2005 16:13 |
| Eclipse User |
|
|
|
Originally posted by: adam.no.spam.cyberspaceroad.spam
On 15/06/05 16:03 Eric Rizzo wrote:
> Dave Wegener wrote:
I'm using Eclipse 3.1 RC1
>> Where is your workspace in relation to the directory that contains the
>> existing source. They should not be in the same directory hiearchy.
All my projects are in my workspace. When I want to work on a project
that is already in CVS but is not on my machine, checking it out from
CVS will put it into my workspace.
>> Workspaces contain references to projects and configuration options
>> you choose. The workspace is used as the default location to create
>> new projects, but any major project that you are working on should not
>> be kept in the workspace. Leave it in the external location and let
>> the workspace reference this location. This will make the CVS
>> management much easier.
>
> I have to disagree that projects should not be kept in the workspace.
> Unless there is a specific reason to have the project's contents be
> located elsewhere, I find it easier to have them in the workspace.
I am following the development environment standards laid down by my
head of department. They are pretty flexible, but they are the same as I
have seen everywhere I've ever worked. "All projects should be in the
same directory x/y/z".
In fact I think if anyone made up these rules again today, they'd do the
same.
|
|
|
| Re: bringing existing project into new eclipse [message #78265 is a reply to message #78136] |
Wed, 15 June 2005 22:35 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Eric Rizzo wrote:
> Dave Wegener wrote:
>> Where is your workspace in relation to the directory that contains the
>> existing source. They should not be in the same directory hiearchy.
>> Workspaces contain references to projects and configuration options you
>> choose. The workspace is used as the default location to create new
>> projects, but any major project that you are working on should not be
>> kept in the workspace. Leave it in the external location and let the
>> workspace reference this location. This will make the CVS management
>> much easier.
> I have to disagree that projects should not be kept in the workspace.
> Unless there is a specific reason to have the project's contents be
> located elsewhere, I find it easier to have them in the workspace.
> Dave, do you have a particular reason for recommending that approach?
> Eric
From a source code management perspective, you don't have to worry about
getting the workspace files mixed up with the project source files. It
may also be a matter of the SCM tool that we use. We have ClearCase. It
maps source to a virtual file system. By keeping the project external to
the workspace, you don't have to copy the entire source tree onto your
harddrive.
It also makes running multiple versions of Eclipse easier. You can have a
separate workspace for each version yet only one copy of the project
source.
To me, workspaces are scratch pad areas. They are easy to create, you can
delete them without worrying about deleting your project source.
|
|
|
|
Powered by
FUDForum. Page generated in 0.08557 seconds
] 
Search
Help
Register
Login
Home
