[jira] Updated: (DERBY-415) sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing

["Andrew McIntyre (JIRA)" <de...@db.apache.org>]

     [ http://issues.apache.org/jira/browse/DERBY-415?page=all ]

Andrew McIntyre updated DERBY-415:
----------------------------------

    Component/s: Tools
                     (was: Services)
     Derby Info: [Patch Available]

Marking patch available, since there is one. I think this patch is an improvement as-is, although it takes a different approach to the issue than what was reported. Perhaps a complete fix would be to add a '-cp db2driver' option that separates the check for db2jcc.jar from the check for derbyclient.jar in ClasspathTester.

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