[Subclipse-users] Re: Checkout project: dependencies not notified?

Thanks for your answer. I know that the way I use Eclipse is common;
that is why I think Subclipse should work properly with that method, as
does the CVS client ;-)

I do not really agree with you though:
- a "clean" followed by a build does *not* fix the problem!
- Going to a new workspace does not fix this: it usually is a problem
when creating a new workspace from scratch because at *that* time you
will checkout complete projects. Once your workspace is underway the
problem no longer occurs as long as you do not checkout new projects.

The stated problem is not a "normal" problem; I've used Eclipse for
years on end using CVS and have *never* got this problem building a new
workspace.

You state that Subclipse is not responsible for notifications to
Eclipse; I think you are wrong there. Eclipse is heavily event driven
and it seems that one crucial event does not get sent... But I guess
I'll have to go to the source to find out ;-)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jan 31 11:44:19 2006