deleted project from trunk to work on branch

[taxeditor.git] / eu.etaxonomy.taxeditor.remoting / src / test / resources / unitils.properties

diff --git a/eu.etaxonomy.taxeditor.remoting/src/test/resources/unitils.properties b/eu.etaxonomy.taxeditor.remoting/src/test/resources/unitils.properties
deleted file mode 100644 (file)
index 3e1d159..0000000
--- a/eu.etaxonomy.taxeditor.remoting/src/test/resources/unitils.properties
+++ /dev/null
@@ -1,68 +0,0 @@
-#\r
-# NOTE: this is the unitils.properties file for the cdmlib-persistence module\r
-# a separate unitils.properties exists for cdmlib-io and for cdmlib-services\r
-#\r
-#\r
-# the list of all properties is found in\r
-# http://unitils.org/unitils-default.properties\r
-#\r
-\r
-### Unitils Modules ###\r
-# List of modules that is loaded. Overloading this list is normally not useful, unless you want to add a custom\r
-# module. Disabling a module can be performed by setting unitils.module.<modulename>.enabled to false.\r
-# If a module's specific dependencies are not found (e.g. hibernate is not in you classpath), this module is not loaded,\r
-# even if it is in this list and the enabled property is set to true. It's therefore not strictly necessary to disable\r
-# any of these modules.\r
-#DEFAULT: unitils.modules=database,dbunit,hibernate,mock,easymock,inject,spring,jpa\r
-unitils.module.easymock.enabled=false\r
-unitils.module.mock.enabled=false\r
-\r
-\r
-### Database ###\r
-#\r
-# Name or path of the user specific properties file. This file should contain the necessary parameters to connect to the\r
-# developer's own unit test schema. It is recommended to override the name of this file in the project specific properties\r
-# file, to include the name of the project. The system will try to find this file in the classpath, the user home folder\r
-# (recommended) or the local filesystem.\r
-#\r
-unitils.configuration.localFileName=unitils-cdmlib-local.properties\r
-\r
-# H2 #\r
-#\r
-database.driverClassName=org.h2.Driver\r
-database.url=jdbc:h2:file:./target/test-classes/h2/cdmTest;AUTO_SERVER=TRUE\r
-database.dialect=h2\r
-database.userName=sa\r
-database.password=\r
-database.schemaNames=PUBLIC\r
-org.dbunit.dataset.datatype.IDataTypeFactory.implClassName.h2=org.dbunit.ext.h2.H2DataTypeFactory\r
-org.unitils.core.dbsupport.DbSupport.implClassName.h2=eu.etaxonomy.cdm.database.H2DbSupport\r
-database.storedIndentifierCase.h2=auto\r
-database.identifierQuoteString.h2=auto\r
-\r
-\r
-#### Transaction mode ###\r
-#\r
-# If set to commit or rollback, each test is run in a transaction,\r
-# which is committed or rolled back after the test is finished.\r
-# Since we have many tests with incomplete data these tests would be\r
-# failing during commit so it is better use rollback as default\r
-# and set commit for individual test where necessary\r
-DatabaseModule.Transactional.value.default=rollback\r
-\r
-# org.unitils.database.transaction.impl.DefaultUnitilsTransactionManager is used by default:\r
-#\r
-#   Implements transactions for unit tests, by delegating to a spring PlatformTransactionManager.\r
-#   The concrete implementation of PlatformTransactionManager that is used depends on the test class.\r
-#   If a custom PlatformTransactionManager was configured in a spring ApplicationContext, this one is used.\r
-#   If not, a suitable subclass of PlatformTransactionManager is created, depending on the configuration\r
-#   of a test. E.g. if some ORM persistence unit was configured on the test, a PlatformTransactionManager\r
-#   that can offer transactional behavior for such a persistence unit is used.\r
-#   If no such configuration is found, a DataSourceTransactionManager is used.\r
-#\r
-# org.unitils.database.transaction.UnitilsTransactionManager.implClassName=org.unitils.database.transaction.impl.SpringTransactionManager\r
-\r
-### Hibernate ###\r
-#\r
-HibernateModule.configuration.implClassName=org.hibernate.cfg.Configuration\r
-\r