[midPoint-git] [Evolveum/midpoint] 081d4d: Adapt failing TestCaseIgnore

[mederly]

  Branch: refs/heads/tmp/mid-6228
  Home:   https://github.com/Evolveum/midpoint
  Commit: 081d4d897e282a7ee30aea9e6b09700f31682262
      https://github.com/Evolveum/midpoint/commit/081d4d897e282a7ee30aea9e6b09700f31682262
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2020-09-24 (Thu, 24 Sep 2020)

  Changed paths:
    M infra/schema/src/main/resources/xml/ns/public/common/common-model-context-3.xsd
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/ContextLoader.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestCaseIgnore.java
    M repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/AbstractIntegrationTest.java

  Log Message:
  -----------
  Adapt failing TestCaseIgnore

Now the resource object is correctly fetched because of assigned
strong mapping. This changed the situation in the repository.

Related to MID-6228.


  Commit: 54a15cd1a6a1765ac6a1af63e7431b0b85dff82d
      https://github.com/Evolveum/midpoint/commit/54a15cd1a6a1765ac6a1af63e7431b0b85dff82d
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2020-09-24 (Thu, 24 Sep 2020)

  Changed paths:
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/traces/OpNodeFactory.java
    A infra/schema/src/main/java/com/evolveum/midpoint/schema/traces/RepositoryCacheOpNode.java
    A infra/schema/src/main/java/com/evolveum/midpoint/schema/traces/RepositoryOpNode.java
    M infra/schema/src/main/resources/xml/ns/public/common/common-model-context-3.xsd
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/Clockwork.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/ClockworkMedic.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/LensContext.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/LensProjectionContext.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/construction/AttributeEvaluation.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/construction/EvaluatedResourceObjectConstructionImpl.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/ActivationProcessor.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/ContextLoader.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/DependencyProcessor.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/Projector.java
    M model/model-impl/src/test/java/com/evolveum/midpoint/model/impl/lens/TestClockwork.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestModelServiceContract.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/sync/TestImportRecon.java
    M model/model-test/src/main/java/com/evolveum/midpoint/model/test/AbstractModelIntegrationTest.java
    M repo/repo-api/src/main/java/com/evolveum/midpoint/repo/api/PreconditionViolationException.java

  Log Message:
  -----------
  Avoid re-processing of completed projections

The most important change is that we no longer clear
synchronizationPolicyDecision for completed projection contexts.
The primary motivation was to avoid loading deleted accounts but
the real consequences are much greater.

At some places (activation processing, assigned construction evaluation)
we added skipping when wave does not match and/or context is completed.

We also skip Projector.projectProjection if context is completed
(the wave check was already in place there).

When evaluating dependencies, we (maybe temporarily) relaxed
BROKEN/IGNORED check in wasProvisioned method. It was not functional
anyway, as synchronizationPolicyDecision was often cleared.

Related to MID-6228.


Compare: https://github.com/Evolveum/midpoint/compare/9531d0e82721...54a15cd1a6a1