Allow user to specify the Oracle JDBC client

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run oracle-ddl2svn against an Oracle instance that has been run through the 
US DoD Security Technical Implementation Guide for Oracle

What is the expected output? What do you see instead?

Instead of connecting to the database to initiate the creation of the DDL for 
the specified schema an ORA-28040 exception is thrown. (No matching 
authentication protocol)

What version of the product are you using? On what operating system?

Using oracle-ddl2svn v1.2 on RHEL 5 and connecting to an Oracle 11gR2 instance.

Please provide any additional information below.

In our environment the Oracle client connecting to the Oracle DB must match the 
version in order to follow the rules of security and information assurance. 
Bundling the Oracle JDBC client JAR might actually be against Oracle's terms of 
use and, in this case, it makes it harder to use your utility. You may want to 
consider allowing the user to specify the path to their local Oracle client 
JAR. 

Original issue reported on code.google.com by wallyatkins on 7 Jun 2011 at 2:33

[GoogleCodeExporter]

Thanks for reporting. I created quick workaround and bundled oracle-ddl2svn  
with latest Oracle jdbc driver. Please, try oracle-ddl2svn version 1.3

Original comment by resh...@gmail.com on 8 Jun 2011 at 10:14

[GoogleCodeExporter]

Not a problem ... I appreciate your quick response. I have downloaded 
oracle-ddl2svn version 1.3 and that allowed me to successfully connect to the 
Oracle instance. Now I have hit an error that I will put in a new Issue.

Original comment by wallyatkins on 8 Jun 2011 at 2:02

[GoogleCodeExporter]

last driver included in bundle

Original comment by resh...@gmail.com on 6 Sep 2011 at 8:45

• Changed state: WontFix