Friday, June 06, 2008

New Best Practices Paper for Subversion and JDeveloper

I've finally got around to pulling together some of the information and best practices that I've blogged about into a document. You can view it here on Oracle Technology Network. Let me know what you think


Dimitri Gielis said...

Hi Susan,

Great document. I also wondered if you do the same for your database objects?
I had some problems with it as I blogged here

I'm using SQL Developer, but I guess it's the same underlaying structure.


Glog said...

The content is very helpful.

The format on OTN is very difficult to read. The text does not wrap.

Kedar said...

Hi Susan,
I'm using JDeveloper version and Tortoise SVN Client:
TortoiseSVN 1.6.5, Build 16974 - 32 Bit , 2009/08/20 08:13:46
Subversion 1.6.5,
apr 1.3.8
apr-utils 1.3.9
neon 0.28.6
OpenSSL 0.9.8k 25 Mar 2009
zlib 1.2.3

Hence I needed to upgrade the SVNKit client in JDeveloper explained in

After upgrading to SVNKit 1.3.1 it started recognizing the SNV files. However authentication started failing while opening history/compare/ pending changes window. I'm able to commit and check out.
Could you please help me?


Susan said...

Hi Kedar,

A couple of things. I don't like to encourage updating SVNKit from third-party sources. Low version SVN clients work with higher level SVN servers. A problem only arises if you are mixing different version clients in the same working copy (for instance if you are using both JDeveloper and another tool like Tortoise on the same working copy).

We did have a bug in 11gR1 that has been fixed in that was released November 10th. Are you able to install this latest version and see if the problem reproduces? This new release support SVN 1.6 server and SVNKit 1.3. Alternatively, can you rollback your changes and use JDeveloper alone to see if the problem reproduces?
See the New Features list on OTN for a full list of SVN supported features in this release - that include merge copy, change lists and a graphical version tree

Anonymous said...

Hi Susan,

The below directories exist for my SOA project. Do you know which ones we DON'T need to check into subversion please?

1) .designer
2) classes
3) deploy
5) testsuites


Susan said...

You do not need to check in classes. The best way to ensure you have all the appropriate directories is to use the Version Application option for initial check in. This ensures that the exclusion list set up in JDeveloper is used.

Anonymous said...

This link seems to have gone missing or been moved. Is there a new one?


Susan said...

the new link for Best Practices is:

for Managing multiple ADF applications with Subversion is: