This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Subversion v1.5 and v1.6 aren't compatible with eachother. It would be nice if one could choose the version that is installed from 'Bundled Subversion Client for Windows'. The other day my Netbeans upgraded that plugin and it broke my SVN checkout since my server is still on v1.5.x (can't update it, haven't got access to that). Also, the plugin description doesn't state which SVN version is supported. Only the version for the plugin is stated (now v0.2.0). I had to revert to using a commandline version for working subversion support in Netbeans. The use of a external version feels slower though. I'm using http://www.sliksvn.com/pub/Slik-Subversion-1.5.7_1-win32.msi , more info: http://www.sliksvn.com/en/download/ To summarize: It should be possible to choose the subversion version which is installed with the 'Bundled Subversion Client for Windows'.
> it broke my SVN checkout since my server is still on v1.5.x It shouldn't be a problem, it often happens that users have a newer client than the one on the server. Sometimes they use a 1.6 client and while having a 1.4 server and it works. What probably happened is that the 1.6 client in the IDE upgraded your working copy to the 1.6 state and your other LOCAL client (sliksvn in your case) was not able to work with the working copy then. But as i said, it should not affect the communication with the server. You should probably upgrade the sliksvn client to a newer version. Is that a problem? What i am trying to say is that this will probably never be implemented. This is not just a problem of the Bundled svn client. There's another bridge module standing between the subversion support and the client itself, it's called svnClientAdapter, which is tightly bound to the version of a svn client used. In 6.9, it's bound to 1.6 and there's no way we can decide which one of this module we use. Commandline client is a slight exception, because it does not have a java interface like other kinds of clients (svnkit or javahl, which is the Bundled svn client's case) and is more loosely coupled.
You are totally right, I made a mistake and should have been referring to the working copy. The server communication still worked properly. On my server though, the SVN client is still on v1.5.x and I can't update that version. So my wish still stands to be able to choose which SVN client version is installed by Netbeans.
(In reply to comment #2) > You are totally right, I made a mistake and should have been referring to the > working copy. The server communication still worked properly. On my server > though, the SVN client is still on v1.5.x and I can't update that version. > > So my wish still stands to be able to choose which SVN client version is > installed by Netbeans. Why this is a problem for me, is because I need to work locally and on the server with the same working copy. That's why I need the same SVN Client version everywhere.