[Subclipse-users] [Subclipse-users] subclipse commit requires update

I am new to svn/subclipse.

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.

It is not possible that anyone else has changed the files in the repo, and
the previous versions of the projects/files in the repo have all been
commited from a single dev environment. So I do not understand why
svn/subclipse nearly always seems to require me to update before I can
commit.

The messages produced are often not very illuminating in terms of exactly
what it thinks needs updating - in some cases referencing '.' for example.

The concern obviously is that what ends up being committed to the repo is
not the exact same project files that are in my working copy when I commit,
if not, then zip is better.

Have I misunderstood what 'update' and 'commit' do ? - or does anyone know
why this happens - or if there is any way of guaranteeing that exactly what
is in my working environment is committed to the repo exactly as-is - a
'forced commit' for example ?

A

-- 
View this message in context: http://www.nabble.com/subclipse-commit-requires-update-tp25461354p25461354.html
Sent from the subclipse - users mailing list archive at Nabble.com.
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2395238
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].