DBSetup wasn't needed in stateful.unit.ExtendedPersistenceUnitTestCase
anyway; it just got in there when I created the standalone test from the
clustered one.
DBSetup is only used in clustered tests now. But since there's nothing
cluster-specific per se about a test wanting to start an HSQL instance
outside the appserver process, I moved DBSetup to org.jboss.ebj3.test.
Logically this could go in the jboss-test.jar, but that would introduce
a dependency on Hypersonic, so probably not worth it.
- Brian
Carlo de Wolf wrote:
I already fixed the classpath. But better to move DBSetup to a
common
package, because you use it in multiple tests.
Carlo
On Wed, 2007-02-21 at 08:38 -0600, Brian Stansberry wrote:
> OK, I'll move DBSetup somewhere where it won't be excluded. All the
> test.clustered* stuff is excluded pending completion of
>
http://jira.jboss.com/jira/browse/JBAS-4125.
>
> Scott M Stark wrote:
>> The org.jboss.ejb3.test.stateful.unit.ExtendedPersistenceUnitTestCase is
>> not building under eclipse because its
>> org.jboss.ejb3.test.clusteredentity.unit.DBSetup import is being
>> excluded from the compile. Either the ExtendedPersistenceUnitTestCase
>> should also be excluded, or the DBSetup exclude removed.