FriendsOfSymfony/FOSRestBundle — pull request #539 by konradpodgorski (2013-08-26 15:07:36+00:00)
Title: Moved dependencies from require-dev to require

Dependencies from require-dev should be moved to require

They are hardcoded in Bundle anyway and cause exceptions when installed in production environment.

Require-dev ( http://getcomposer.org/doc/04-schema.md#require-dev )
*Lists packages required for developing this package, or running tests, etc.*

Most of developers could miss that problem because we usually work in dev environment and later install application through deployment scripts which usually use composer.lock file.

I left empty require-dev on purpose, let me know if you disagree with that.

### Examples of hard coded dependencies

**JMS/SerializerBundle dependency**

```
php app/console container:debug

[Symfony\Component\DependencyInjection\Exception\InvalidArgumentException]
Unable to replace alias "jms_serializer.serializer" with "fos_rest.serializer".

[Symfony\Component\DependencyInjection\Exception\InvalidArgumentException]
The service definition "jms_serializer.serializer" does not exist.
```

**JMS/SerializerBundle and Sensio\FrameworkExtraBundle dependency**
at the beginning

```
use Symfony\Bundle\FrameworkBundle\Templating\TemplateReference;

use Sensio\Bundle\FrameworkExtraBundle\EventListener\TemplateListener;

use JMS\Serializer\SerializationContext;
```

https://github.com/FriendsOfSymfony/FOSRestBundle/blob/master/EventListener/ViewResponseListener.php