No, I just ran it once with the default (which I guess is jdk14). I had been under the mistaken impression that derbyall included some jdk13 tests.

David

Mamta Satoor wrote:

Hi David,

In my environment, I first do the setup for jdk14 and then run derbyall. Next, if my change warrants testing in jdk13 too, then I rerun derbyall in jdk13 environment. When you ran derbyall, did you run it twice, once in jdk14 and then in jdk13? Mamta On 6/13/05, *David Van Couvering* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Hi, Mamta.  I am trying to figure out how I missed this -- shouldn't my
    derbyall run have failed?  I was assuming derbyall runs for both jdk14
    and jdk13.  Am I mistaken?

    Thanks,

    David

    Mamta Satoor wrote:

     > Hi,
     >
     > As part of checkin 179696 for "Derby-305 Fix error messages in
     > properties files to match text in documentation", the jdk13
    master for
     > updatable resultset test got overwritten with jdk14 master ie
    after that
     > checkin, if you did a diff between
     >
    
java\testing\org\apache\derbyTesting\functionTests\master\updatableResultSet.out
     >
     > (this is master for jdk13) and
     >
    
java\testing\org\apache\derbyTesting\functionTests\master\jdk14\updatableResultSet.out
     > (this is master for jdk14+), you wil see that there is no
    difference. I
     > have attached the correct master for jdk13 to this mail. Can I
    commiter
     > please commit it to
     > java\testing\org\apache\derbyTesting\functionTests\master.
     >
     > thanks,
     > Mamta


Reply via email to