db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-415) sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing
Date Fri, 14 Apr 2006 01:06:00 GMT
    [ http://issues.apache.org/jira/browse/DERBY-415?page=comments#action_12374445 ] 

Bryan Pendleton commented on DERBY-415:
---------------------------------------

Since it's valid to use the db2jcc driver to access Derby, and since there are certainly users
doing so, I think it's nice that sysinfo supports db2jcc, so I don't think we should remove
that support entirely.

What if we made it so that:
 - if you've got both derbyclient.jar and db2jcc.jar in your classpath, -cp prints info about
both of them
 - if you've got neither of them, -cp prints the "NOT FOUND IN CLASSPATH" messages
 - if you've got one of the drivers in your classpath, but not the other, then -cp prints
info about the one you have, but is silent about the one you do not have.

That is, we could make it print the alarming "NOT FOUND IN CLASSPATH" only if you have *neither*
driver in your classpath, but as long as you have at least one of the drivers in your classpath,
we could omit the NOT FOUND messages for the other driver.

Would that be an improvement?


> 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
>         Type: Bug

>   Components: Services
>     Versions: 10.1.1.0
>     Reporter: David Van Couvering
>     Priority: Minor

>
> 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


Mime
View raw message