| overlapping projects problem [message #257490] |
Thu, 01 July 2004 09:57  |
Eclipse User |
|
|
|
I have an existing cvs structure where eclipse makes life somewhat
difficult:
module/
./src
./test
I want src and test to have their own project.
Within an existing workspace I was able to create the two projects by
specifying that the projects be located in the workspace -- not in the
above directories.
Then I shared the projects and ended up with the following:
module/ (.project, .classpath)
./src
./test (.project, .classpath)
Where src and test were linked/external folders.
Then I rechecked out the cvs module (using smartcvs) and attempted to
import these two projects into a new workspace (attempting to simulate
how others on my team would work).
But when I do so, eclipse does not recreate the same projects as above.
The .project and .classpath files are shown the project, the CVS
directories are shown in the project. I cannot also impor the test
project, as it now overlapping with the first project.
(BTW, I really can't checkout the modules directly into eclipse because
I need much other stuff from cvs that other tools use concurrently with
eclipse.)
Is this just a no-go with eclipse?
-bk
|
|
|
| Re: overlapping projects problem [message #257498 is a reply to message #257490] |
Thu, 01 July 2004 10:14  |
| Eclipse User |
|
|
|
I see a bit more clearly now. More info on my directories:
cvs.checkout/
./module
./src
./test
eclipse.workspace
./module (.project, .classpath)
./bin
./src (linked to src above)
When I checked in the .project/.classpath files from eclipse.workspace,
they went into the cvs repository and thus appeared in the cvs.checkout
directory after an update.
It was from the cvs.checkout that I tried to subsequently import the
projects into a new workspace. But of course from that directory the
actual subdirectories exist and I did not get the same project structure.
Since I want to be able to checkout all of cvs.checkout with any cvs
tool and be able to any IDE (well, eclipse and idea) I need for the
..project/.classpath to be under the cvs.checkout tree.
So, I guess I will try something like:
cvs.checkout/
./module
./eclipse
./src (.project, .classpath)
./test (.project, .classpath)
./src
./test
The downside is that I must now defined variables to avoid having
full-paths in the projects linked directories.
eclipse could be nicer if:
1. It allowed for explicitly naming its project control files (eg,
".src-project, .src-classpath, .test-project, .test-classpath). Then I
would be able to keep these files in the module root.
2. Allow for overlapping projects as long as the proper directory
excludes are defined. (I think this may be supported. But without #1 I
still have to create subdirectories for the project files and variables
to avoid full-paths.)
Am I way off? Is there an easier way?
-bk
|
|
|
Powered by
FUDForum. Page generated in 0.36115 seconds
Home