[
https://issues.apache.org/jira/browse/DERBY-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark B updated DERBY-4183:
--------------------------
Attachment: status.diff
I'm adding the status changes; currently it looks as though, now that I
manually cleared some of the cruft that the tests accumulate in
java/testing/system, java/testing/logs, etc all tests are good; there had been
some database access trouble in the interim
that makes me think perhaps I should modify the junit-clean script to properly
clean that cruft?
as all the test jars are in
/java/testing/org/apache/derbyTesting/functionTests, a bzipped tarball of that
is 6MB
One more question that arises is, I've managed to give my system a java 1.4.2
alternate installation though the precise interaction of the j14lib /
java14compile.classpath properties is a low priority as it stands; do I need to
make [java-version-] conditional scripts for compiling the test jars? I'd
understand from what I see that providing the test jars are compiled in the
java version that handles the tests, then all is good
Best regards
Mark
> Our regression tests use various jar files for which we don't have build
> scripts.
> ---------------------------------------------------------------------------------
>
> Key: DERBY-4183
> URL: https://issues.apache.org/jira/browse/DERBY-4183
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.6.0.0
> Reporter: Rick Hillegas
> Attachments: status.diff, testjars.diff, testjars.diff
>
>
> We should add build scripts for these jar files. This is a mini-project
> suitable for a newcomer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
