[
https://issues.apache.org/jira/browse/DERBY-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964360#comment-13964360
]
Myrna van Lunteren commented on DERBY-6532:
-------------------------------------------
To my surprise, the sysinfo output wouldn't work for me in one windows
environment either...
And then I noticed that where it worked, I had junit.jar in the CLASSPATH...
Choosing BaseTestCase as the indicator class was not the right thing to do, as
it extends junit classes and so cannot get loaded by the classloader without
junit.jar available...
derbyTesting.jar does contain some non-junit tests...
I'll pick some other class...I'm thinking of
- one of the system tests or an old harness test
but: if ever all tests get converted to junit we'll have to adjust this
sysinfo code too.
- add a dummy class somewhere that does not get used anywhere.
note: would need to verify build includes it
increase in size of derbyTesting.jar would be negligible.
> sysinfo does not show derbyTesting package info on linux
> --------------------------------------------------------
>
> Key: DERBY-6532
> URL: https://issues.apache.org/jira/browse/DERBY-6532
> Project: Derby
> Issue Type: Bug
> Components: Test, Tools
> Affects Versions: 10.10.1.4, 10.11.0.0, 10.10.2.0
> Reporter: Myrna van Lunteren
>
> Although the file org/apache/derby/info/tsting.properties may be present, on
> Linux, calling sysinfo does not show the version number for derbyTesting.jar.
> See for more info DERBY-6468.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
