Mark,
one other thing - if I do then attempt to do an 'update' on the (now
deleted) directory - which seems like a reasonable thing - *given* that it
appears to think that this is out-of-date - then, if I try to commit - I get
a (tree) 'conflict in the working copy obstructs the current operation ....
so still havent been able to commit the project.
Andrew J G wrote:
>
> Mark,
>
> I think that I understand most of what was in those links. I will post
> when I see things that dont seem to fit.
>
> One of the things that I have noticed a number of times is what seems to
> me to be odd behaviour when I delete directories from within the IDE.
>
> For example - I have a project - in that project there was a directory
> which contains some redundant source code. I deleted the source code files
> from within the IDE - then committed the entire project - that works fine.
> Then I delete the (empty) directory - again within the IDE - the
> appropriate 'cross' symbol appears next to the directory entry.
>
> However, now if I try to commit the entire project - this commit fails -
> telling me that the corresponding directory in the repo is 'out of date'.
> Here the whole project was commited immediately before the directory was
> deleted - so the repo version should definately be 'up-to-date'.
>
> I guess that - depending on how the delete is actally implemented - the
> working copy may have 'lost' the local meta-data for the deleted directory
> - making this a tricky thing to get right - but I don't see why it seems
> to think that an update is required.
>
> Andrew
>
>
>
> Mark Phippard-3 wrote:
>>
>> On Tue, Sep 15, 2009 at 4:38 PM, Andrew J G <andrew.gray_at_rcrt.co.uk>
>> wrote:
>>> I am new to svn/subclipse.
>>
>> See this explanation:
>>
>> http://markphip.blogspot.com/2006/12/mixed-revision-working-copies.html
>>
>>> As I understand it - in normal use - 'update' brings my working version
>>> 'up
>>> to date' with the repo, and 'commit' posts my working version to the
>>> head of
>>> the repo.
>>>
>>> I have a dedicated svn repo for several development projects - to
>>> provide
>>> version control - this one is not currently shared with anybody else.
>>>
>>> What I see - almost every time that I try to commit a project is that
>>> the
>>> commit initially fails - complaining that files are 'out of date' - and
>>> advising me to do an update first - before trying to commit.
>>
>> You are probably getting the errors on folders. There are a handful
>> of operations that require the folder to be at HEAD, such as modifying
>> the properties of the folder. So even though you are the only one
>> working your working copy can get out of date.
>>
>> This is all core Subversion stuff, it is not caused by Subclipse.
>>
>> We used to have a feature to help make this more clear, but people
>> were so annoyed by it we turned it off by default. See:
>>
>> http://markphip.blogspot.com/2006/12/subclipse-synchronize-feature-show-out.html
>>
>> --
>> Thanks
>>
>> Mark Phippard
>> http://markphip.blogspot.com/
>>
>> ------------------------------------------------------
>> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2395249
>>
>> To unsubscribe from this discussion, e-mail:
>> [users-unsubscribe_at_subclipse.tigris.org].
>>
>>
>
>
--
View this message in context: http://www.nabble.com/subclipse-commit-requires-update-tp25461354p25476285.html
Sent from the subclipse - users mailing list archive at Nabble.com.
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2395638
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-09-16 18:44:45 CEST