This content has been marked as final. Show 6 replies
The problem is with svnkit. Until now sqldeveloper use version 1.1.6.
You can fix this with svnkit 1.2. You have to download it from http://www.svnkit.com/org.tmatesoft.svn_1.2.0.standalone.zip and put some files into sqldeveloper extension directory.
- svnkit-javahl.jar (rename into svnjavahl.jar)
from svnkit 1.2 to
It works for me.
note: the svn repository is a source code repository. (.java .class and .sql files.)There are arguments both ways, but the current implementation in SQLDeveloper only supports version control on source files. IMO there needs to be a link between the vc repository, the source file you are working on and the object it creates in the database.
there is no DB data there, and no DB schema. (other than in the .sql files)
I'm saying this because I'm not an SQL specialist, (and even then, I'm mainly mysql!) and I seem to get the impression that source control to SQL guys might mean something slightly different. i.e. versioning a DB rather than the source code that creates a DB. If I'm wrong about this, apologies! ;)
As it stands, you can edit and compile a procedure in the database, but if you don't remember to extract it back to its source file, you end up with a mismatch. Similarly, if you edit the source file and forget to run it into the database you end up with a mismatch.
Yeah, that should have been addressed right from the beginning...
For now, you can still vote on the feature request asking to combine file and internal editor (the solution to versioning, compiling and running/debugging): http://htmldb.oracle.com/pls/otn/f?p=42626:39:2572465713320559::NO::P39_ID:3262, so you add weight for implementing sooner.
I just copied/replaced/renamed files according to these instructions but only get an error message
SEVERE 37 0 oracle.ide.IdeCore Exception firing addinsLoaded to oracle.jdevimpl.vcs.VCSManagerImpl$7@1966070
when I start SQL Developer. This is with SQL Developer 1.5.4 and SVNkit 1.3.0 on WinXP.