che-server/core
Sergii Leschenko 787041dd4e Rework mechanism to TckListener instead of TckModuleFactory (#2953)
It solves two problems:
- we initialize test instances with new injectors instead of
  using default child injector mechanism. It resolves issues
  with injection of injector in GuiceEntityListenerInjectionManager.
- we add ability to clean resources after tck test finish.
  So it allow close entity manager after after tck tests with jpa
  and resolve problems with reusing static fields by eclipse link
  by EntityManagerFactory when different tests in one module use it
2016-11-03 10:41:06 +02:00
..
che-core-api-core [maven-release-plugin] prepare for next development iteration 2016-10-26 09:37:49 +00:00
che-core-api-dto [maven-release-plugin] prepare for next development iteration 2016-10-26 09:37:49 +00:00
che-core-api-dto-maven-plugin [maven-release-plugin] prepare for next development iteration 2016-10-26 09:37:49 +00:00
che-core-api-jdbc [maven-release-plugin] prepare for next development iteration 2016-10-26 09:37:49 +00:00
che-core-api-jdbc-vendor-h2 CHE-2015 Rename configuration properties 2016-10-27 17:29:46 +03:00
che-core-api-model [maven-release-plugin] prepare for next development iteration 2016-10-26 09:37:49 +00:00
che-core-typescript-dto-maven-plugin [maven-release-plugin] prepare for next development iteration 2016-10-26 09:37:49 +00:00
commons Rework mechanism to TckListener instead of TckModuleFactory (#2953) 2016-11-03 10:41:06 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-10-26 09:37:49 +00:00