Comments on: JDeveloper and Subversion http://technology.amis.nl/2006/12/18/jdeveloper-and-subversion-2/ Friends of Oracle and Java Tue, 21 Oct 2014 18:48:09 +0000 hourly 1 http://wordpress.org/?v=4.0 By: shay http://technology.amis.nl/2006/12/18/jdeveloper-and-subversion-2/#comment-4140 Wed, 11 Apr 2007 02:01:28 +0000 http://technology.amis.nl/blog/?p=1441#comment-4140 Here is the workaround:
http://forums.oracle.com/forums/thread.jspa?messageID=1772827

]]>
By: M McCowan http://technology.amis.nl/2006/12/18/jdeveloper-and-subversion-2/#comment-4139 Tue, 19 Dec 2006 16:11:41 +0000 http://technology.amis.nl/blog/?p=1441#comment-4139 I ran across the same problem after upgrading to the newest version of TortiseSVN. According to the Subversion documentation, the 1.4 client upgrades any working copy it accesses to the new format. The version of JavaSVN that JDeveloper uses is a 1.3-based client thus can’t read the 1.4 format.

I think I read a thread on Oracle’s JDeveloper forum where someone had replaced JavaSVN with a new version or was using a different client altogether in order to access a 1.4 working copy.

]]>
By: David Edwards http://technology.amis.nl/2006/12/18/jdeveloper-and-subversion-2/#comment-4138 Mon, 18 Dec 2006 17:08:26 +0000 http://technology.amis.nl/blog/?p=1441#comment-4138 Would you be using JDeveloper and TortoiseSVN on the same working copy? A subversion 1.3 client can check out / update / commit from a subversion 1.4 repository but as soon as a subversion 1.4 client operates on a 1.3 working copy. A modification occurs to the .svn directory so that a subversion 1.3 client does not understand the .svn structure or format. This is what I have found. I believe that the subversion 1.4 repository is using different structure from 1.3. and that a seemless conversion is performed when talking to 1.3 client

]]>