You could try removing the 2nd execution that dbunit has - the one
that populates the database after tests are run:

               <executions>
                   <execution>
                       <id>test-compile</id>
                       <phase>test-compile</phase>
                       <goals>
                           <goal>operation</goal>
                       </goals>
                   </execution>
                   <execution>
                       <!-- Runs before integration tests and jetty:run-war -->
                       <id>test</id>
                       <phase>test</phase>
                       <goals>
                           <goal>operation</goal>
                       </goals>
                   </execution>
               </executions>

Matt

On 5/16/07, Steve Tynor <[EMAIL PROTECTED]> wrote:
The build fails.   Surefire reports all tests pass:

 > Results :
 > [surefire] Tests run: 57, Failures: 0, Errors: 0

then maven reports build failure:

 > [INFO] [dbunit:operation {execution: test}]
 > [INFO]
------------------------------------------------------------------------
 > [ERROR] BUILD ERROR
 > [INFO]
------------------------------------------------------------------------
 > [INFO] Error executing database operation: CLEAN_INSERT
 >
 > Embedded error: Database may be already open: Locked by another
process [90020-34]

Steve

On 5/15/2007 11:35 PM, Matt Raible wrote:
> Is this an error that causes the build to fail, or just something you
> see after all the tests finish running?
>
> On 5/15/07, Steve Tynor <[EMAIL PROTECTED]> wrote:
>> Thanks Matt.  I thought shutdown=true should do the trick too.  For what
>> it's worth, I get a similar error with H2 (again, after 100% successful
>> Junit):
>>
>>  >  Embedded error: Database may be already open: Locked by another
>> process [90020-34]
>>
>> so it may be related to other changes I've made to the project.  Anyone
>> care to offer ideas of what I should be looking for?
>>
>> Steve
>>
>> On 5/15/2007 10:41 PM, Matt Raible wrote:
>> ...
>> > The fact that you have ;shutdown=true in your jdbc.url should handle
>> > this.  It also might be related to the following issue:
>> >
>> > http://jira.codehaus.org/browse/MOJO-673
>> >
>> > Have you tried using H2?
>> >
>> > Matt
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to