Started by GitHub push by ledsoft00443762953762951.0052065206626a5334b16d97d900b8d3ddcbb13ddb4dfec04f8eea5334b16d97d900b8d3ddcbb13ddb4dfec04f8eeorigin/developmenta5334b16d97d900b8d3ddcbb13ddb4dfec04f8eea5334b16d97d900b8d3ddcbb13ddb4dfec04f8eeorigin/developmenta5334b16d97d900b8d3ddcbb13ddb4dfec04f8eea5334b16d97d900b8d3ddcbb13ddb4dfec04f8eeorigin/developmenthttps://github.com/kbss-cvut/jopa.git04395879testReportfalse#626376295408252JOPA Development #626626falsefalse626860SUCCESS1760425587284https://kbss.felk.cvut.cz/jenkins/view/Java%20Tools/job/JOPA-Development/626/jopa-impl/src/test/java/cz/cvut/kbss/jopa/oom/metamodel/PolymorphicEntityTypeResolverTest.javajopa-integration-tests/src/main/java/cz/cvut/kbss/jopa/test/runner/RetrieveOperationsWithInheritanceRunner.javajopa-integration-tests/src/main/java/cz/cvut/kbss/jopa/test/query/runner/PolymorphicSelectQueryRunner.javajopa-impl/src/main/java/cz/cvut/kbss/jopa/oom/metamodel/PolymorphicEntityTypeResolver.javac783dcf672541e5ac8d4d6f027f2f91b58ace6601760014677000https://kbss.felk.cvut.cz/jenkins/user/ledvima1Martin Ledvinkamartin.ledvinka@fel.cvut.czAlways resolve entity type to the most specific available. This changes entity type resolution behavior but should not break applications (Liskov principle). It is more consistent with JPA and common sense. 2025-10-09 14:57:57 +0200c783dcf672541e5ac8d4d6f027f2f91b58ace660Always resolve entity type to the most specific available.editjopa-integration-tests/src/main/java/cz/cvut/kbss/jopa/test/query/runner/PolymorphicSelectQueryRunner.javaeditjopa-integration-tests/src/main/java/cz/cvut/kbss/jopa/test/runner/RetrieveOperationsWithInheritanceRunner.javaeditjopa-impl/src/test/java/cz/cvut/kbss/jopa/oom/metamodel/PolymorphicEntityTypeResolverTest.javaeditjopa-impl/src/main/java/cz/cvut/kbss/jopa/oom/metamodel/PolymorphicEntityTypeResolver.javajopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/ReadOnlyUnitOfWork.javajopa-impl/src/main/java/cz/cvut/kbss/jopa/oom/EntityConstructor.javajopa-impl/src/test/java/cz/cvut/kbss/jopa/sessions/ReadOnlyUnitOfWorkTest.javajopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/cache/CacheManager.javajopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/cache/LruCacheManager.javajopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/cache/EntityCache.javajopa-integration-tests/src/test/java/cz/cvut/kbss/jopa/test/integration/ReadOnlyEntityManagerCacheTest.javaa5334b16d97d900b8d3ddcbb13ddb4dfec04f8ee1760425559000https://kbss.felk.cvut.cz/jenkins/user/ledvima1Martin Ledvinkamartin.ledvinka@fel.cvut.czUse instantiable Java type in EntityConstructor to create entity instance. Relevant for scenarios when generated change-tracking subclasses are used by JOPA. 2025-10-14 09:05:59 +0200a5334b16d97d900b8d3ddcbb13ddb4dfec04f8eeUse instantiable Java type in EntityConstructor to create entity instance.editjopa-integration-tests/src/test/java/cz/cvut/kbss/jopa/test/integration/ReadOnlyEntityManagerCacheTest.javaeditjopa-impl/src/main/java/cz/cvut/kbss/jopa/oom/EntityConstructor.javaeditjopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/ReadOnlyUnitOfWork.javaeditjopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/cache/CacheManager.javaeditjopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/cache/LruCacheManager.javaeditjopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/cache/EntityCache.javaeditjopa-impl/src/test/java/cz/cvut/kbss/jopa/sessions/ReadOnlyUnitOfWorkTest.javagithttps://kbss.felk.cvut.cz/jenkins/user/ledvima1Martin Ledvinka