Related question: http://stackoverflow.com/questions/38636186/how-to-create-zf3-console-application

@fedys I think you're mis-diagnosing the root cause. The EventManagerAwareInitializer only resets the EM instance if one is not already present in the instance (see the lines immediately preceding the one you linked).

Note: I'm not saying the problem doesn't exist; I'm saying that the diagnosis is likely incorrect. I'll see if I can resolve it shortly.

@weierophinney The problem I described really exists. The root cause is $eventManager->getSharedManager() returns null and therefore the second part of the condition is not met.

The problem is in zend-mvc's SendResponseListener implementation/service configuration.

SendResponseListener will lazy-load an event manager instance if none is already present when getEventManager() is invoked; however, the instance is created with no arguments, which means that with zend-eventmanager v3, no shared manager is present. Also in v3, there is no way to inject a shared manager after the fact; it must be injected at instantiation (this was a change made to aid performance).

The solution will be to provide a factory for the SendResponseListener within zend-mvc that pulls the EventManager service and pushes it into a new SendResponseListener instance.

You can test this locally in the meantime. Create a factory class as follows, in module/Application/src/SendResponseListenerFactory.php (or module/Application/src/Application/SendResponseListenerFactory.php, if still using a PSR-0 structure from an older application):

namespace Application;

use Interop\Container\ContainerInterface;
use Zend\Mvc\SendResponseListener;

class SendResponseListenerFactory
{
    public function __invoke(ContainerInterface $container)
    {
        $listener = new SendResponseListener();
        $listener->setEventManager($container->get('EventManager'));
        return $listener;
    }
}

Add the following to module/Application/config/module.config.php:

'service_manager' => [
    'factories' => [
        \Zend\Mvc\SendResponseListener::class => \Application\SendResponseListenerFactory::class,
    ]
]

In addition to the above, I tested by adding a single console route, and adding console usage via the Application\Module::getConsoleUsage() method. I can verify that all works as expected once the new factory is registered; without the factory registered, no output is generated.

I'll get a PR ready for zend-mvc shortly, and tag this and other related issues when it's ready to merge.

To get the fix, please update your zend-mvc to 3.0.3:

$ composer require "zendframework/zend-mvc:^3.0.3"