[midPoint-git] [Evolveum/midpoint] be8d2a: Adapt TestGrouperAsyncUpdate

[mederly]

  Branch: refs/heads/feature/live-sync-unification
  Home:   https://github.com/Evolveum/midpoint
  Commit: be8d2a12d2852655a693aa0e5ba37883ecba3729
      https://github.com/Evolveum/midpoint/commit/be8d2a12d2852655a693aa0e5ba37883ecba3729
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2021-02-01 (Mon, 01 Feb 2021)

  Changed paths:
    M testing/story/src/test/java/com/evolveum/midpoint/testing/story/grouper/AbstractGrouperTest.java
    M testing/story/src/test/java/com/evolveum/midpoint/testing/story/grouper/TestGrouperAsyncUpdate.java
    A testing/story/src/test/resources/grouper/task-async-update.xml

  Log Message:
  -----------
  Adapt TestGrouperAsyncUpdate


  Commit: 42848afaebe505fac35951ef5d4e9a92c9138267
      https://github.com/Evolveum/midpoint/commit/42848afaebe505fac35951ef5d4e9a92c9138267
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2021-02-01 (Mon, 01 Feb 2021)

  Changed paths:
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/ChangeExecutor.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/ContextLoader.java

  Log Message:
  -----------
  Stop unlinking broken-being-deleted shadows

Originally the projCtx.isDelete method returned "false" for broken
contexts, even if the shadow deltas was DELETE. This was perhaps not
quite correct, so in 0bb36defb29448ba326713a8642439a64ba93160 we changed
this behavior. Now broken-being-deleted contexts have isDelete=true.

This means that such shadows started to be unlinked. It is maybe not
right (at least TestServiceAccounts.test104 thinks so). Therefore, here
we restore the original behavior of unlinking: broken-being-deleted
contexts are NOT unlinked.


Compare: https://github.com/Evolveum/midpoint/compare/923b958a0cfd...42848afaebe5