Timestamps of checked out files

[Tom Quarendon]

Has there ever been a problem in SVNKit whereby files get the commit timestamp when you check them out, rather than the checkout timestamp? Looking at the source code the current version appears to at least process and do things with the "use-commit-time" svn configuration option, but I don't know whether this has always been the case.
We're getting a problem with luntbuild where updated files have the commit timestamp, and from the source code of luntbuild it just uses a simple invocation of SVNKit passing in a default options object, so I don't think that there's anything in luntbuild explicitly provoking or overriding the behaviour. So I'm hoping that it was once a problem in SVNKit that has been fixed and that a simple jar substitution will solve the issue.

[Alexander Kitaev-3]

Hello Tom,

I couldn't recall any problems with that option.

> invocation of SVNKit passing in a default options object, so I don't think
Default options objects reads default Subversion configuration file that
is located at ~/.subversion/config (on Linux) and also read values from
/etc/subversion/config (on Linux). On Windows these files are located in
the Application Data catalog of the current and default users.

So, please make sure none of configuration files owned by luntbuild
process user doesn't contain 'use-commit-time=yes' option or better put
'use-commit-time=no' into configuration file.

SVNKit will use new option value as soon as you change configuration
file (it checks file's timestamp).

Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java [Sub]Versioning Library!

Tom Quarendon wrote:

> Has there ever been a problem in SVNKit whereby files get the commit
> timestamp when you check them out, rather than the checkout timestamp?
> Looking at the source code the current version appears to at least process
> and do things with the "use-commit-time" svn configuration option, but I
> don't know whether this has always been the case.
> We're getting a problem with luntbuild where updated files have the commit
> timestamp, and from the source code of luntbuild it just uses a simple
> invocation of SVNKit passing in a default options object, so I don't think
> that there's anything in luntbuild explicitly provoking or overriding the
> behaviour. So I'm hoping that it was once a problem in SVNKit that has been
> fixed and that a simple jar substitution will solve the issue.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: svnkit-users-unsubscribe@...
For additional commands, e-mail: svnkit-users-help@...