[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] Why doI have upcoming changes after a commit?(single user)

From: jambalaya <incog_83_at_wp.pl>
Date: 2006-10-08 16:40:47 CEST

I'm new here so hello!
tools: eclipse 3.2, subclipse 1.1.4 and newer
I crate a project, write some files and classes, then I choose Team -> Share
project and I choose to share only the src folder and other files I would
like (I ommit the .classpath and .project and bin). The project is shared no
problem.
Then, to check if all works I choose New project -> from SVN and choose a
host and the project. The wizxard let's me configure it with the New Project
wizxard becouse I don't have the .project file. Sweet, that's what I wanted.
Next, I make a synchro and choose to ignore the bin folder and the
.classpath and .project files. Subclipse sends a commit becouse I changed
the dirs properties (I tihnk?).
And now I'm ready to work on my local copy. I edit the files and choose Team
-> Synchronize and see the out-going changes, so I make a commit.
Immediately afterwards i synchronize again, and I hav upcoming chamges - all
the dirs which contained the files I've just commited. Why does it happen? I
have the most recent working copy, don't I? Is this a bug or am I doing
something wrong? The problem existed even if I dodn't fiddle with the bin
and other project specific files. Please answer.
Pozdro!

-- 
View this message in context: http://www.nabble.com/Why-doI-have-upcoming-changes-after-a-commit-%28single-user%29-tf2405131.html#a6704610
Sent from the subclipse - users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Oct 8 16:40:55 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.