Check why copyComponentIntoNewProject may be called with a non-project contained Component
In ComponentLibraryUtils, line 87, a null check is involved triggering another null check in TestCaseSimulator. This null check should not be needed since the file project can never be null if the component is correctly embedded in the file project.
- The null checks should be removed.
- It should be investigated under which conditions a wrong containment may occur. This may be due to some running test case, or a wrong deletion order. However, this problem should be resolved where it emerges.
(from redmine: issue id 3523, created on 2018-09-21, closed on 2019-09-30)