From 345a32ec3eea9203e869cb22307868bfcd7b0c6a Mon Sep 17 00:00:00 2001 From: Ingo Schommer Date: Tue, 7 May 2013 10:51:47 +0200 Subject: [PATCH] Remove require-dev section, composer doesn't handle it well Any "composer require " call will first call a "composer update". This *automatically* includes dev requirements, without providing a way to turn off this behaviour. A workaround would be "composer require --no-update && composer update --no-dev ", but that drastically reduces the usefulness of the command for our target audience (moderately technical devs). In the end, the small faction of devs needing the dev dependencies also know how to install them on their own. And having a local phpunit build actually gets in the way more than it helps in case you have it installed through PEAR already (can get really weird when using the PEAR provided "phpunit" binary, but the autoloader finds the composer managed classes). --- composer.json | 6 ------ 1 file changed, 6 deletions(-) diff --git a/composer.json b/composer.json index c4689f1..162cb0d 100644 --- a/composer.json +++ b/composer.json @@ -7,12 +7,6 @@ "silverstripe/framework": "3.0.*@stable", "silverstripe-themes/simple": "*" }, - "require-dev": { - "silverstripe/docsviewer": "*", - "silverstripe/behat-extension": "*", - "silverstripe/buildtools": "*", - "phpunit/phpunit": "3.7.*" - }, "config": { "process-timeout": 600 },