Can you tell us exactly what you are trying to do when you come across these
problems. If you are modifying the structure of directories/renaming files
you need to make sure to do it using the tools. Either by using tortoise to
rename them, or having subclipse rename them. This way they will know what
the other is doing. If you are just moving files using file system
commands, then neither will know what's going on.
On 7/26/06, Bill Ewing <firstname.lastname@example.org> wrote:
> We use Tortoise SVN 1.3,5 and Subclipse 1.0.3. These are the latest
> We periodically get Tortoise or Subclipse to fail to work correctly.
> For example, if we try to do a clean up, we get a "path is not a working
> copy" message.
> If we try to do an update, we get "attempted to lkock an already locked
> The way we get into trouble is by deleting, copying or moving files in or
> out of the folders in question. We can appreciate how Eclispe may need to
> be Refresh'ed when we do things "behind its back," but are amazed at how,
> when we do something incredibly simple in "full view of Tortoise or
> subclipse" that the latter sometimes goes into a left hand doesn't know what
> the right hand is doing debacle.
> In the past we've usually been able to hurl combinations of Refresh's,
> Update's, Clean Up's and Resolve's to simply make the nuisance messages get
> out of the way, but currently, we're locked up.
> Whether this is a bug or not, it is certainly in our minds, brought on by
> the simplest and commonest actions and therefore we feel SVN is, at best, a
> fair tool that has some treacherous and time wasting pitfalls.
> Because we have experienced this same problem for over a year on several
> different PC's and over several versions of Eclipse and several versions of
> Tortoise and subclipse, we have to believe that the community at large
> simply does not have this problem or denies it existence.
> Can anyone offer any suggestions?
Received on Wed Jul 26 18:41:46 2006