Perhaps the custom file selector was causing some problems. I did add a
path element to the definition of the file selector so that it had
access to the jar.driver.
-Original Message-
From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 9:52 AM
To: Ste
It is very strange that copying the file to the lib dir makes things
work. I tried to replace where in build.xml jar.driver is set to hsql,
but that didn't worked also.
Any ideas?
Aleksandar Kostadinov wrote:
> Yeah, I see that the problem is not finding the jdbc driver. I meant
> that all other
I did not touch the build script at all as part of that previous
commit...
From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 8:37 AM
To: Steve Ebersole
Cc: hibernate-dev@lists.jboss.org
Subject: Re: Hibernate test sui
Yeah, I see that the problem is not finding the jdbc driver. I meant
that all other databases tests fail with a new reason, but the same for
all of them.
I asked you if there is a change in how hibernate searches for it.
Cruisecontrol invokes ant with the following pratameters:
-Djar.driver=${drive
No the failures are different. Previously we were getting NPE; now CCE.
The tests run fine for me in my IDE. The only way I have been able to
reproduce such a CCE is for the JDBC driver to be unavailable when the
junit task starts up. This causes the constructor of one of the test
classes to fa
Only hsql tests work.
Other databases tests fail with the same reason.
Is there a change in the way testsuite should be ran? How to set jdbc
driver? Properties file changes?
Steve Ebersole wrote:
>I am just now checking in the reorganization of the Hibernate test suite
>I have been working on f
