Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <462148956.1252332537643.JavaMail.jira@brutus>
Date: Mon, 7 Sep 2009 07:08:57 -0700 (PDT)
From: "Mark B (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4183) Our regression tests use various jar
 files for which we don't have build scripts.
In-Reply-To: <562511593.1240503271610.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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

Hi,

so it looks as though the signed jar aspect is mostly a red herring; as I would have hoped a signature won't be necessary for *every* checksum; it seems as though some of the wrong checksums are deliberate - though the checksum aspect perhaps needs documenting as I've mostly simply imported the old [often apparently wrong] checksums as manifest file entries; there is one place that a signed jar is necessary, so I've added ant script to generate the necessary key then sign;

one of the jars is a database, so it really would be unwieldy uncompressed, I've made a zip of it to then compile the jar from;

generally of course I would possibly need an svn branch to commit the binary changes to - alternatively I could make a tarball of the java/testing/ directory; the actual jar changes may safely be omitted, I suppose I'd svn rm the jars themselves as there is now the dynamic generation;

basically for jar files that are compiled from source, I'm creating directories containing the source files, then recompiling from there;  I've included the test-jar creation in the 'normal' ant build, though all the test-jar creation could be put into its own directory as an independent jar build;

I'd be happy to hear your comments so far - it needs some additional testing though I seem to have managed the main hurdles

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: 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.