On Thu, Mar 29, 2007 at 11:06:57AM -0400, Mark Phippard wrote:
> On 3/29/07, Jens Seidel <jensseidel@users.sf.net> wrote:
> I noticed that subclipse uses the (modification) time stamp of the
> affected file on the server when updating files. This results in files
> with a future time stamp on my system which confuses make. Subversion
> (svn update) uses the local host time instead.
>
> I use Linux, SVNKit, Subclipse 1.2.0 and eclipse 3.3M5eh.
>
> Should I open a bug report?
>
>
> Subclipse does not touch your files. Subversion does it via the API call (such
> as update) that we make. Subversion has two options here. The default is to
> set the time to current time. You can modify this via the config file in ~
> /.subversion to "Use-commit-time".
Thanks, I didn't know about this option.
> It sounds like you have that setting defined. If the command line is behaving
> differently, you might want to check your preferences in Eclipse. Open to Team
> -> SVN and see if you overrode the location of the config files. It could be
> that the API when used via Subclipse is being pointed at a different config
> file.
My config was right (tried default and pointed to my local copy).
> Finally, if after all that you think there is a bug, you would want to send the
> relevant information to support@svnkit.com.
I did so and they fixed two problems related to timestamps. SVNKit used
use-commit-times = yes
as default which is different from subversions default. Also this option
was sometimes ignored and not evaluated. It's fixed in rev 3023.
PS: Please note that I was not able to test timestamps if the working
copy is on a mounted remote filesystem. Maybe it should be tested as
well ...
Jens
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Apr 3 00:47:13 2007