SVNKit Connector locks working copy database even when no team command is running
Summary
As soon as SVNKit connector is selected all opened working copies in Eclipse get their database locked. This does not happen with the Native JavaHL connector. Locking the working database means that other clients like the command line or TortoiseSVN can not be used in conjuction with Eclipse/Subversive.
Steps to reproduce
- Open a project in a repo from Eclipse.
- Execute SVN update from the command line or another client like TortoiseSVN.
- Result: svn: E200033: Another process is blocking the working copy database, or the underlying filesystem does not support file locking; if the working copy is on a network filesystem, make sure file locking has been enabled on the file server svn: E200033: sqlite[S5]: database is locked svn: E200042: Additional errors: svn: E200033: sqlite[S5]: database is locked
Expected change
The working copy database should only be locked when a SVN command is being executed.
Affected versions
- Eclipse Version: 2022-09 (see: Help | Eclipse IDE)
- Subversive Version: 4.8.0 (see: Help | Eclipse IDE | Installation Details -> search for 'Subversive')
- Subversive Connector Version: 6.1.0 (SVNKit) vs 6.0.0 (Native JavaHL 1.9.3) (see same search dialog as above)