<dependency>
<groupId>hsqldb</groupId>
<artifactId>hsqldb</artifactId>
<version>1.8.0.7</version>
</dependency>
maybe there is a newer version available ;)
In OpenJPAs persistence.xml I use the following settings:
<persistence-unit name="TestUnit">
<properties>
<property name="openjpa.jdbc.DBDictionary" value="hsql" />
<property name="openjpa.ConnectionDriverName"
value="org.hsqldb.jdbcDriver" />
<property name="openjpa.ConnectionURL" value="jdbc:hsqldb:mem:test"
/>
<property name="openjpa.ConnectionUserName" value="sa" />
<property name="openjpa.ConnectionPassword" value="" />
</properties>
</persistence-unit>
LieGrue,
strub
--- On Thu, 10/21/10, Kevin Meyer - KMZ <[email protected]> wrote:
> From: Kevin Meyer - KMZ <[email protected]>
> Subject: Re: Failing tests on SQL Integration
> To: [email protected]
> Date: Thursday, October 21, 2010, 6:10 PM
> Hi Mark,
>
> Could you provide me with some assitance here - I assume
> this (just)
> requires setting up an appropriate profile in the sql pom?
>
> Regards,
> Kevin
>
> On 21 Oct 2010 at 13:21, Mark Struberg wrote:
>
> > hmm, In general any PostgreSQL tests should only be
> performed in a
> > special IT (IntegrationTest) Profile. Most tests
> should run
> > perfectly fine with an in-memory derby or hsql
> database).
> >
> > LieGrue,
> > strub
>
>
