db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark B (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4183) Our regression tests use various jar files for which we don't have build scripts.
Date Fri, 04 Sep 2009 15:40:57 GMT

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

Mark B updated DERBY-4183:

    Attachment: testjars.diff


well derby does seem a nice project, so I'm looking at the automatic compilation of test jars;

I've written a patch that re-compiles for instance the jar found at java/testing/org/apache/derbyTesting/functionTests/testData/v1/j1v1.jar

my work so far raises the relevant questions
- without sight of the original commands it's partly guesswork trying to re-compile the jars
- specifically, in the case of j1v1.jar there are manifest entries for signing; the only reference
in the project to ant's signjar command is in the demo directory, java/demo/localcal/build.xml
that calls for local signature details;

so it's unclear to me whether I should be signjar-ing the jars, whose key should sign it /
whether I simply [as the patch currently does] add the original signature manifest entries
to the jar?

Best regards


> 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:
>            Reporter: Rick Hillegas
>         Attachments: 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.

View raw message