If there is a targetId, there must be a target. Otherwise

- someone have removed the target dynamically and forgot to remove the
  targot from the pedestrian's target list (which is a bug)

- or there is another bug that must be fixed

There was a
assert targetIds.size() > 0

That means, this case is not expected, right?
Why is this case handled then in the next lines?

I switched the assert statement against getNextTargetId() which throws
an exception if there is no next target.

Use hasNextTarget() if you have to check this.

It testet for a normal resource file, but unit tests have a different
resource folder. So this cannot be testet.

Update PedestrianEvacuationTimeProcessor manually in EvacuationTimeProcessor since you cannot assume that the PedestrianEvacuationTimeProcessor gets updated automatically.

Before this, models had to periodically check (in update()) if a agent
reached its target. With this, models can register a target listener.
The listener are called by the target controller. The implementation can
change the model state.

To prevent MigrationManager from upgrading