gbrodman e0e348183d Use the DatabaseMigrationSchedule to determine which TM to use (#1233) ... * Use the DatabaseMigrationSchedule to determine which TM to use We still allow the "manual" specification of a particular transaction manager, most useful in @DualDatabaseTest classes. If that isn't specified, we examine the migration schedule to see which to return. Notes: - This requires that any test that sets the migration schedule clean up after itself so that it won't affect future test runs of other classes (because the migration schedule cache is static) - One alternative would, instead of having a "test override" for the transaction manager, be to examine the registry environment and only override the transaction manager in the UNIT_TEST environment. This doesn't work because there are many instances in which tests simulate non-test environment.		2021-07-14 13:05:01 -04:00
..
gradle/dependency-locks	Remove the use of GCS APIs provided from GAE SDK (#1228)	2021-07-13 14:52:37 -04:00
src	Use the DatabaseMigrationSchedule to determine which TM to use (#1233)	2021-07-14 13:05:01 -04:00
WEB-INF/appengine-generated	Enable Cloud SQL when Datastore is enabled for unit test (#502)	2020-03-10 12:26:25 -04:00
build.gradle	Remove the use of GCS APIs provided from GAE SDK (#1228)	2021-07-13 14:52:37 -04:00
Dockerfile	Build docker image of nomulus tool (#142)	2019-07-16 20:18:44 -04:00