[
https://issues.apache.org/jira/browse/DERBY-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-6468:
--------------------------------------
Attachment: DERBY-6468_2.diff
Attaching a second version of the patch - this cleans up a couple of changes
that I do not remember making (one additional import, one modified comment) in
the sysinfo Main class, and further modifies the build.xml to move the new
org/apache/derby/info/tsting.properties file into derbyTesting.jar, and also
generates this file when we build the testing classes.
I ran all sysinfo related tests separately, and they passed both with classes
and (sane) jars, except for SysinfoAPITest, which failed with jars, but that's
a known problem (DERBY-2343), which is why that test doesn't run currently.
I think having another version number file in the derbyTesting.jar may make
that bug worse, at least I got a different result from the test compared to how
it runs with jars in an environment that doesn't have my changes, but I think
that's something to be figured out in relation to that bug...
I'll run full tests now to be on the safe side, then commit if ok.
> Add a version number to derbyTesting.jar
> ----------------------------------------
>
> Key: DERBY-6468
> URL: https://issues.apache.org/jira/browse/DERBY-6468
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Rick Hillegas
> Attachments: DERBY-6468_1.diff, DERBY-6468_2.diff
>
>
> The product jars carry version stamps in property files stored in the
> org/apache/derby/info directory. It would be good for the test jar to carry a
> version stamp too. This can be useful in verifying that the tests are at the
> right revision level tor the product being tested.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
