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] Updated: (DERBY-415) sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing
Date Sat, 15 Apr 2006 16:54:01 GMT
     [ http://issues.apache.org/jira/browse/DERBY-415?page=all ]

Bryan Pendleton updated DERBY-415:

    Attachment: derby-415.diff

Attached is derby-415.diff, a patch proposal.

This change modifies the behavior of -cp as follows:
 - if you run "java sysinfo -cp", then if you have either the jcc driver or the derby
   network client in your classpath, that is treated as success. If you have
   neither driver, then a failure is reporting listing both libraries as failed.
 - if you run "java sysinfo -cp client", then we assume that you are specifically
   interested in the client JDBC drivers, so we report a failure for either missing
   library. The only way to have success with "-cp client" is to have both.

This is not exactly what David asked for. In his case, he wanted "-cp client"
to treat the case where you have the Derby Network Client, but *not* the JCC
driver, as a success.

This patch behaves that way with plain old "-cp", but not with "-cp client". My feeling was
that if you specifically said "-cp client", you wanted to get all the details about the client
JDBC library portion of your classpath, so such a person might well care about whether or
not the JCC library was found. But maybe I'm just being over-cautious here.

Please have a look at this patch and tell me what you think.

> 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:
>     Reporter: David Van Couvering
>     Assignee: Bryan Pendleton
>     Priority: Minor
>  Attachments: derby-415.diff
> If you run
>   java org.apache.derby.tools.sysinfo -cp client SimpleApp.class
> you get
>     Derby Client libraries (derbyclient.jar)
>     user-specified class (SimpleApp)
>     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:
For more information on JIRA, see:

View raw message