Deletion of packages results in fatal error
Most package operations (package:delete, package:deactivate etc.) and possibly also flow3:cache:flush result in a fatal error like this one:
$ ./flow3 package:delete TYPO3.T3con11Typo3Org Flushed all caches. Fatal error: Call to a member function dispatch() on a non-object in /opt/local/apache2/htdocs/sites/flow3.org/Packages/Framework/TYPO3.FLOW3/Classes/SignalSlot/SignalAspect.php on line 49
[BUGFIX] package:* commands no longer issue a fatal error
Most package:* commands and sometimes also the flow3:cache:flush
command issued a fatal error. The actual command was executed
successfully, but the SignalAspect caused a fatal error because
the proxy code cache had already been flushed and therefore
FLOW3 was in an unstable state.
Those commands which flush the code caches will now exit right away
to avoid any further code execution.