<p dir="auto">After symfony/dev-master had a merge comment, I am also unable to installe a fresh version of 2.5.6. When for example trying to clear cache for prod environment, I get:</p>
<p dir="auto">PHP Fatal error:  Class 'Symfony\Component\HttpKernel\EventListener\TranslatorListener' not found in project_path/symfony/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/ContainerAwareEventDispatcher.php on line 142</p>
<p dir="auto">When SF2.1.5 was out, there was a new parameter 'kernel.trusted_proxies' in the framework that ended up in an issue when cache:clear was run in production that made some installations crash.</p>
<p dir="auto">This problem and its solution was explained here: <a href="http://symfony.com/blog/symfony-2-0-21-and-2-1-5-released" rel="nofollow">http://symfony.com/blog/symfony-2-0-21-and-2-1-5-released</a></p>
<p dir="auto">For us, the only thing that worked was to run rm -rf app/cache/prod in all our Apache servers (about 100 machines) and regenerate cache folders with cache:warmup</p>
<p dir="auto">We also temporally changed our deployment scripts to do this all the time, but I guess using cache:clear is a much better option, isn't it?</p>
<p dir="auto">Is there any way to improve cache:clear command so that it does not crash when new parameters are added or the only way to go is to manually remove the cache to be 100% sure?</p>
<p dir="auto">Please, note that there are already quite a bunch of big Symfony2 projects that cannot risk to crash in production because a new optional parameter has been added.</p>
<p dir="auto">We're rsyncing instead of a symlink + folder switching strategy to deploy. Second option would have worked, but this is not the point.</p>
<p dir="auto">Anyway, if the only way to be 100% sure is either cache removing or folder switching we will reconsider our deployment strategy in order to use it (which if I am not wrong is what Capifony does).</p>
<p dir="auto">Waiting for your thoughts on that</p>