[ 
http://issues.apache.org/jira/browse/DERBY-1619?page=comments#action_12425076 ] 
            
Rajesh Kartha commented on DERBY-1619:
--------------------------------------

I tried the v2 of the patch with some special characters and that seem to work 
fine. The Derby jars 
are located in C:\temp\{}Test % '[EMAIL PROTECTED] and the sysinfo now shows:

--------- Derby Information --------
JRE - JDBC: J2SE 5.0 - JDBC 3.0
[C:\temp\{}Test % '[EMAIL PROTECTED] 10.2.0.5 alpha - (427819M)
[C:\temp\{}Test % '[EMAIL PROTECTED] 10.2.0.5 alpha - (427819M)
[C:\temp\{}Test % '[EMAIL PROTECTED] 10.2.0.5 alpha - (427819M)
[C:\temp\{}Test % '[EMAIL PROTECTED] 10.2.0.5 alpha - (427819M)
------------------------------------------------------

i tried it using the java command:
C:\temp\{}Test % '[EMAIL PROTECTED]>java -cp 
.\derby.jar;.\derbyclient.jar.\derbytools.jar;.\derbyrun.jar;.\derbynet.jar 
org.apache.derby.tools.sysinfo

I think setting the  CLASSPATH variable (or any other environment variable on 
the WIndows command prompt for that matter) with these special characters in 
the directory path does not work, hence could not try sysinfo using the jars in 
the CLASSPATH.

> Sysinfo in 10.2  shows multiple entries if the derby jars reside in a 
> directory with spaces in its name
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1619
>                 URL: http://issues.apache.org/jira/browse/DERBY-1619
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.2.0.0
>         Environment: Windows XP, jdk 1.5
>            Reporter: Rajesh Kartha
>         Assigned To: Andrew McIntyre
>             Fix For: 10.2.0.0
>
>         Attachments: derby-1619-v1.diff, derby-1619-v2.diff
>
>
> For the Derby jars residing in C:\Documents and Settings\Administrator\TEMP 
> DIR\lib, the sysinfo shows:
> --------- Derby Information --------
> JRE - JDBC: J2SE 5.0 - JDBC 3.0
> [C:\Documents%20and%20Settings\Administrator\TEMP%20DIR\lib\derby.jar] 
> 10.2.0.5 alpha - (426734)
> [C:\Documents%20and%20Settings\Administrator\TEMP%20DIR\lib\derbytools.jar] 
> 10.2.0.5 alpha - (426734)
> [C:\Documents%20and%20Settings\Administrator\TEMP%20DIR\lib\derbynet.jar] 
> 10.2.0.5 alpha - (426734)
> [C:\Documents%20and%20Settings\Administrator\TEMP%20DIR\lib\derbyclient.jar] 
> 10.2.0.5 alpha - (426734)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derby.jar] 10.2.0.5 
> alpha - (426734)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derbynet.jar] 10.2.0.5 
> alpha - (426734)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derbyclient.jar] 
> 10.2.0.5 alpha - (426734)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derbytools.jar] 
> 10.2.0.5 alpha - (426734)
> [C:\Documents%20and%20Settings\Administrator\TEMP%20DIR\lib\db2jcc.jar] 2.6 - 
> (90)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\db2jcc_license_c.jar] 
> 2.6 - (90)
> ------------------------------------------------------
> This is a regression from 10.1 where the same sysinfo shows:
> --------- Derby Information --------
> JRE - JDBC: J2SE 5.0 - JDBC 3.0
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derby.jar] 10.1.3.2 - 
> (426741)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derbynet.jar] 10.1.3.2 
> - (426741)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derbyclient.jar] 
> 10.1.3.2 - (426741)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\derbytools.jar] 
> 10.1.3.2 - (426741)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\db2jcc.jar] 2.6 - (90)
> [C:\Documents and Settings\Administrator\TEMP DIR\lib\db2jcc_license_c.jar] 
> 2.6 - (90)
> ------------------------------------------------------

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

        

Reply via email to