Hi,
My repository is full of Eclipse projects that depend on each other
(meaning project A's Java Build Path -> Projects tab refers to projects
C and D). This is a great way to develop because it is immediately clear
what subprojects are used by a given project.
In the above case, if i check out project A into an empty workspace then
Eclipse will report a building error like "Project
lib-apache-commons-modeler-1.1 is missing required Java project:
'lib-apache-commons-digester-1.7' ". If I now go back to the svn
repository browser and check out projects B and C then Eclipse should
notice that those projects have become available and notify the builder.
This however does not use, and Eclipse keeps on telling me that those
projects are not available even though they are present in the
workspace. Even a "build all" does not fix this; the only ways to get
project A to compile are:
- remove project B and C from the build path; close the dialog and watch
some errors; add them back.
- Do a "Close Project" on projects B and C followed by an Open Project.
This behaviour does work correctly with the CVS client so it seems to be
related to the checkout process of Subversion.
I used Subversion 1.2.3 and 1.3.0, and I use the latest subclipse at
this time (0.9.105).
Greetings,
Frits Jalvingh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Jan 25 01:17:45 2006