On 2017-10-19 10:44, Johan Corveleyn wrote:
> I have no idea what ISVNClient.getChangelists corresponds to compared
> with the native 'svn' commandline. But one thing that might be
> relevant: in the client-side configuration file 'config' there are two
> properties that can have a big influence here:
>
> (see %APPDATA%/Subversion/config on Windows, or ~/.subversion/config on Unix)
> [[[
> ### Section for configuring working copies.
> [working-copy]
> ### Set to a list of the names of specific clients that should use
> ### exclusive SQLite locking of working copies. This increases the
> ### performance of the client but prevents concurrent access by
> ### other clients. Third-party clients may also support this
> ### option.
> ### Possible values:
> ### svn (the command line client)
> # exclusive-locking-clients =
> ### Set to true to enable exclusive SQLite locking of working
> ### copies by all clients using the 1.8 APIs. Enabling this may
> ### cause some clients to fail to work properly. This does not have
> ### to be set for exclusive-locking-clients to work.
> # exclusive-locking = false
> ]]]
>
> So with the above options you can make all clients (that use that
> config file) respect "exclusive-locking" (with the exclusive-locking
> flag), or just a subset of specific client applications (with the
> exclusive-locking-clients property).
>
> Perhaps your commandline 'svn' invocation uses the standard
> ~/.subversion/config file, which has the exclusive-locking flag set,
> and your SmartSVN application might use another one (it can choose
> another "config dir").
Thank you for this suggestion. I've tried with
exclusive-locking = true
but it makes no difference. I don't know what to enter for
exclusive-locking-clients =
How does SVN detect the client name when using JavaHL?
--
Best regards,
Thomas Singer
=============
syntevo GmbH
http://www.syntevo.com
http://www.syntevo.com/blog
Received on 2017-10-19 14:07:07 CEST