Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Fri, 17 Mar 2006 18:06:56 +0100
From: Andreas Korneliussen <Andreas.Korneliussen@Sun.COM>
Subject: Re: regression ?! all tests in jdbcapi fails for me
In-reply-to: <441AD2FC.6020901@Sun.COM>
To: derby-dev@db.apache.org
Reply-to: Andreas.Korneliussen@Sun.COM
Message-id: <441AECB0.3080809@sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5 (X11/20060113)
References: <441ACA4D.6010006@sun.com> <441AD2FC.6020901@Sun.COM>


> 
> So I guess something must be off with your build or run environment.
> I built Derby with "ant clobber && ant buildsource && ant testing && ant 
> buildjars". I use the &&'s beacuse I have had problems combining build 
> targets on the same ant command line before.
>

Thank you for the help figuring this out.

I copied the jarfiles you had built, and reran the test. It failed the 
same way.

The reason the test failed seems to be the way you order the jarfiles in 
the classpath.

* Running the test with the derbyclient.jar before derby.jar in the 
classpath, caused the failures, imo.


This classpath caused all tests in jdbcapi to fail for me:
Java classpath: 
/home/ak136785/devel/issue/919/trunk//jars/sane/derbyclient.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derby.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derbytools.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derbynet.jar:/usr/local/share/java/db2jcc/lib/db2jcc.jar:/usr/local/share/java/db2jcc/lib/db2jcc_license_c.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derbyTesting.jar:/home/ak136785/devel/issue/919/trunk//tools/java/jakarta-oro-2.0.8.jar:/home/ak136785/devel/issue/919/trunk//tools/java/junit.jar

With this classpath, I could run the tests with no errors:
Java classpath: 
/home/ak136785/devel/issue/919/trunk//jars/sane/derby.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derbyclient.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derbytools.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derbynet.jar:/usr/local/share/java/db2jcc/lib/db2jcc.jar:/usr/local/share/java/db2jcc/lib/db2jcc_license_c.jar:/home/ak136785/devel/issue/919/trunk//jars/sane/derbyTesting.jar:/home/ak136785/devel/issue/919/trunk//tools/java/jakarta-oro-2.0.8.jar:/home/ak136785/devel/issue/919/trunk//tools/java/junit.jar

I think this is a regression from previous behaviour.  The last time I 
did svn up, I think was earlier this week, or last week, so I think this 
may have been introduced this week.

Andreas