[
https://issues.apache.org/jira/browse/DERBY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748320#comment-13748320
]
Myrna van Lunteren commented on DERBY-2343:
-------------------------------------------
I think this is referring to the fact that sometimes people (accidentally) load
two derby(*).jar files on their CLASSPATH. And I think sysinfo can only reflect
one.
So if someone hangs a derby.jar from 10.10.1.1 and 10.8 in the CLASSPATH, it
will likely only show the first one, or at least only reflect the version of
the first one.
> sysinfo API only returns correct information for the first jar file on the
> classpath
> ------------------------------------------------------------------------------------
>
> Key: DERBY-2343
> URL: https://issues.apache.org/jira/browse/DERBY-2343
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
> Reporter: Andrew McIntyre
> Priority: Trivial
> Labels: derby_triage10_5_2
>
> While updating the sysinfo_api test to our current JUnit usage, I
> rediscovered the problem which has kept this test from running on a regular
> basis: when running the test from jar files, only the first jar file on the
> classpath properly reports its information through the sysinfo API.
> It is not a security manager issue, as disabling the security manager did not
> solve the problem. There may be jar-sealing issues involved, but I haven't
> looked into the issue very deeply. Just noting the issue here for later
> investigation.
> I will commit a patch which updates the current sysinfo_api test to be called
> SysinfoAPITest, and also add a note to tools._Suite about the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
