[ http://issues.apache.org/jira/browse/DERBY-415?page=all ]
Bryan Pendleton updated DERBY-415:
----------------------------------
Attachment: derby-415-cp-db2driver.diff
I think that Andrew's idea about adding a new argument: '-cp db2driver' is a
very good one.
Attached is derby-415-cp-db2driver.diff, which adds support for "-cp db2driver"
and changes
"-cp client" so that it only refers to the Derby Network Client. Thus the new
behavior is:
java sysinfo -cp ===> checks all the various components of the
classpath
java sysinfo -cp client ===> just checks whether the network client is in
the classpath
java sysinfo -cp db2driver ==> just checks whether the JCC driver is in the
classpath
I think this patch provides a much better solution to the original problem
observed by David.
Please have a look.
> sysinfo with -cp client option should not print error saying DB2 jar file and
> driver class are missing
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-415
> URL: http://issues.apache.org/jira/browse/DERBY-415
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.1.1.0
> Reporter: David Van Couvering
> Assigned To: Bryan Pendleton
> Priority: Minor
> Attachments: derby-415-cp-db2driver.diff, derby-415.diff
>
>
> If you run
> java org.apache.derby.tools.sysinfo -cp client SimpleApp.class
> you get
> FOUND IN CLASS PATH:
> Derby Client libraries (derbyclient.jar)
> user-specified class (SimpleApp)
> NOT FOUND IN CLASS PATH:
> Derby Client libraries (db2jcc.jar)
> (com.ibm.db2.jcc.DB2Driver not found.)
> The "NOT FOUND IN CLASSPATH" output is confusing and invalid because we're
> testing the network client, not the DB2 JCC client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
