You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2015/01/22 01:39:36 UTC

[jira] [Updated] (DERBY-2343) sysinfo API only returns correct information for the first jar file on the classpath

     [ https://issues.apache.org/jira/browse/DERBY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren updated DERBY-2343:
--------------------------------------
    Issue Type: Improvement  (was: Sub-task)
        Parent:     (was: DERBY-6164)

> 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: Improvement
>          Components: Tools
>    Affects Versions: 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
>            Reporter: Andrew McIntyre
>            Assignee: ahsan shamsudeen
>            Priority: Trivial
>              Labels: derby_triage10_5_2, gsoc2013
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)