[ http://issues.apache.org/jira/browse/DERBY-1152?page=comments#action_12432990 ] Bryan Pendleton commented on DERBY-1152: ----------------------------------------
Hi Susan, thanks for having a look at this! I believe that the output is correct, and reflects an important difference between derby.jar and derbytools.jar: derby.jar has an entry in its Manifest file which automatically loads all of the locale-specific properties jars, whereas derbytools.jar doesnt. That is, when your classpath specifies only derby.jar, but you also have the local jars in the same physical directory as derby.jar, the Java class loader reads the Manifest classpath entry and automatically loads the locale jars when it loads derby.jar. But derbytools.jar, which omits that special Manifest entry, does not automatically load those Manifest jars. Sysinfo, in my opinion, is faithfully reporting the actual environment as it finds it, and that environment, with respect to the locale jars in the classpath, is indeed different in this case. > Failures in sysinfo and sysinfo_withproperties induced by classpath wiring > -------------------------------------------------------------------------- > > Key: DERBY-1152 > URL: http://issues.apache.org/jira/browse/DERBY-1152 > Project: Derby > Issue Type: Bug > Components: Test > Affects Versions: 10.2.1.0 > Reporter: Rick Hillegas > Assigned To: Bryan Pendleton > Fix For: 10.2.1.0 > > Attachments: derby-1152-looser-policy.diff > > > If you wire your classpath together out of the compiled classtree and the > checked-in jars, you get the following error in the sysinfo and > sysinfo_withproperties tests. You don't see this error if you run against the > built Derby jar files: > 15d14 > < Unable to analyze class path: access denied (java.util.PropertyPermission > java.class.path read) > 43d41 > < Unable to analyze class path: access denied (java.util.PropertyPermission > java.class.path read) > 72d69 > < Unable to analyze class path: access denied (java.util.PropertyPermission > java.class.path read) > Test Failed. -- 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
