Diagnosing Problems with Subversion Integration
If any problem occurs with Subversion integration, feel free to contact our support. To facilitate detecting, locating, and resolving your issue, provide detailed information regarding your Subversion integration with CLion. This topic lists the necessary information and explains how you can retrieve it.
The following data is usually required to diagnose Subversion problems:
the CLion version and the build number,
the operating system used.
General VCS settings
The general version control settings applied to your project are specified on the Version Control page of the Settings/Preferences dialog. Open the Settings / Preferences Dialog by pressing Ctrl+Alt+S or by choosing for Windows and Linux or for macOS, and click Version Control.
Subversion-specific settings are configured on the Subversion page, under the Version Control node of the Settings/Preferences dialog. Open the Settings / Preferences Dialog by pressing Ctrl+Alt+S or by choosing for Windows and Linux or for macOS, and click Subversion under Version Control.
Local working copy format
The working copy format is the Subversion format in compliance with which the working copy was created. To view the working copy format, choose View | Tool Windows | Version Control on the main menu. In the Version Control tool window that opens, switch to the Subversion Working Copies Information tab.
Parent folders of the branches used
To view the configuration of branches, in the Subversion Working Copies Information tab of the Version Control tool window, click the Configure Branches link.
Enabling svnkit logging
If data saved in the CLion logs is not sufficient to solve the problem and the problem is related to the communication protocol or authentication, enable svnkit logging, reproduce the problem, and attach the
To enable svnkit logging, add
-Djavasvn.log=true to one of the following files depending on the operating system used:
Refer to Tuning CLion to learn about CLion
vmoptions files locations.