Re: tests corrupting existing database

> > Mick; are you sure you haven't been running tests against a production
> > instance?
> 
> This is exactly the type of answer i was hoping for :-)
>  and certainly fits the picture.
> i'll investigate and post again.

you are right jorge. thank god i was just slow ;-)

I see that maven.test.skip=true can be added to build.properties.

But isn't kinda dangerous to be running tests against one's configured
database!?

Should we not always run tests against a separate hypersonic database?
(Ok i understand that this then stops testing the other databases, but
the test database should be overridable if you do in fact want to use
the same database. There seem to be separate property keys already for
test, ie scarab.test.database.., which are currently just match the
scarab.database.. equivalent properties).

~mck

-- 
"Little things affect little minds." Disraeli 
| semb.wever.org | sesat.no | sesam.no |

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkge0GMACgkQkdPrePiuutP/PQCfXXUJ7sA3RP9IiaFiVeonx3PV
F0MAn1iFlsWZkfNB5D/N4PWGmYIeEpo1
=MC02
-----END PGP SIGNATURE-----