I also noticed this "feature".
You probably had been using Sync view to run updates, so it may not
propagate revision to the folder in some cases.
My workaround is to run update from the package explorer or
navigator, then commit on properties will work.
I wonder if it would be difficult to expose commit sets that belong
to each individual transaction on a Sync view and let user to run update
per transaction...
regards,
Eugene
Szloboda Zsolt wrote:
> when I try to set a property on a directory
> (with the Team/Set Property command)
> and then I try to commit the changes
> (with the Team/Commit... command)
> I get the following error:
>
> 'propset someproperty "somevalue" C:/Temp/svntest/TestProject
> commit -m "" -N C:/Temp/svntest/TestProject
> Sending Temp/svntest/TestProject
> Merge conflict during commit
> svn: Commit failed (details follow):
> svn: Your file or directory '.' is probably out-of-date
> svn: The version resource does not correspond to the resource within the
> transaction. Either the requested version resource is out of date (needs to
> be updated), or the requested version resource is newer than the transaction
> root (restart the commit).'
>
> (however I CAN set properties on files!)
>
> the repository is absolutely new
> I have just imported my project
> (it was fully synchronized before I set the property)
> and no other operation is performed on it
>
> Subversion version is 1.1
> Subclipse version is 0.9.105
> Eclipse version is 3.1.1
>
> the painful thing about this is
> that I cannot use the Configure Branches/Tags function
> as it should set a property on a directory (I guess)
> and the commit fails in this case also
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Jan 19 08:40:35 2006