Do you have Tools > Preferences > Code Editor > Start in Read Only mode checked off? And what about the impact of clicking on the Pencil icon in the code editor toolbar? If controlling the read/write mode via standard preference and editor features do not help with SVN managed files, then you have probably found a bug.
SQL Developer Team
sorry for the late reply.
The preference 'Start in Read Only mode' is off.
What do you mean with the 'Pencil icon'? it is not on the toolbar.
You are correct: when editing a file under SVN version control, the Pencil icon does not show up in the PL/SQL code editor toolbar as it normally does with non-version controlled files. In the same way, Start in Read Only mode has no effect for version controlled files.
Anyway, the scenario you describe seems to work for me, using 4.0.2 with a 1.7.17 CollabNet SVN client install. A file, once committed with the svn:needs-lock property, can be checked out again as a working copy that must be explicitly locked before the code editor can access it as writable. The only thing I noticed not working was this preference:
Tools > Preferences > Versioning > General > Automatically Lock Files with svn:needs-lock Property after Check Out
When that is checked off, it displays a dialog with a list of all the svn:needs-lock files that it fails to lock upon Check Out.
What do you mean with the CollabNet SVN client? All actions I described were executed using SQLD only.
Guess it isn't necessary, it's just the SVN client I use on WIndows to do command line (svn and svnadmin) stuff. I typically use an SVN plug-in in Eclipse, and occasionally the SVN command line client.
did you try the described scenario using SQLD only?, or did you use the Windows SVN client tools for locking?