| Folder deletion weirdness [message #559210] |
Wed, 15 September 2010 21:06  |
Eric Jain Messages: 266 Registered: July 2009 |
Senior Member |
|
|
After deleting a folder in Eclipse I'm often unable to commit:
Some of selected resources were not committed.
svn: Commit failed (details follow):
svn: Item 'xxx' is out of date
svn: DELETE of 'xxx': 409 Conflict (https://localhost)
Even though no one else has touched that folder and no incoming changes or conflicts are shown, I end up having to revert the change and delete the folder a second time. After that I am usually able to commit.
Anyone else notice such behavior? I'm using the Subversive Team Provider 0.7.9 with SVNKit 1.3.2 on Helios (win64).
|
|
|
|
| Re: Folder deletion weirdness [message #559358 is a reply to message #559273] |
Thu, 16 September 2010 09:05   |
|
Originally posted by: steven.whatmore.purefacts.com
I have noticed the same behavior and it is a real PITA (Pain in the A$$)
As far as I am concerned the client should know this and handle it
appropriately.
"Alexander Gurov" <alexander.gurov@polarion.com> wrote in message
news:i6sltd$o29$1@build.eclipse.org...
> Hello Eric,
>
> This happened because Subversive keeps version not only for files but for
> folders too. So, if the folder version is changed on the server side you
> need to update it first and only then commit deletions or additions on
> your side.
|
|
|
|
| Re: Folder deletion weirdness [message #559475 is a reply to message #559273] |
Thu, 16 September 2010 14:18  |
Eric Jain Messages: 266 Registered: July 2009 |
Senior Member |
|
|
| Alexander Gurov wrote on Thu, 16 September 2010 04:53 | This happened because Subversive keeps version not only for files but for folders too. So, if the folder version is changed on the server side you need to update it first and only then commit deletions or additions on your side.
|
I'm quite certain that no one else had touched that part of the repository. Even so, shouldn't the synchronize view show a conflict and give me the option to either override and commit or override and update (rather than show an error on commit)?
I remember being able to avoid this problem by using the JavaHL connector instead of SVNKit, but I can no longer verify that as I'm now running on a 64 bit platform.
Trying to create a simple test case that demonstrates this problem, but no luck so far...
|
|
|
Powered by
FUDForum. Page generated in 0.01589 seconds