You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/03/25 18:12:22 UTC

[jira] [Commented] (DERBY-6468) Add a version number to derbyTesting.jar

    [ https://issues.apache.org/jira/browse/DERBY-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946805#comment-13946805 ] 

Rick Hillegas commented on DERBY-6468:
--------------------------------------

Thanks, Myrna. Looks like you've added a new file to derbyTesting.jar to hold the version number of the testing classes. That's exactly what I was hoping to see. Once that's checked in, we should be able to get the unit tests to report the contents of that file and verify that it agrees with the version stamps in the product jars. Thanks!

> 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
>
>
> 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)