minor #13624 removed composer --dev option everywhere (fabpot)

This PR was merged into the 2.3 branch.

Discussion
----------

removed composer --dev option everywhere

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

0fe4913 renamed composer.phar to composer to be consistent with the Symfony docs
af59316 removed composer --dev option everywhere
This commit is contained in:
Fabien Potencier 2015-02-10 09:04:11 +01:00
commit 9a70bbbdb2
34 changed files with 36 additions and 36 deletions

View File

@ -36,10 +36,10 @@ before_install:
- if [ "$TRAVIS_BRANCH" = "master" ]; then export COMPOSER_ROOT_VERSION=dev-master; else export COMPOSER_ROOT_VERSION="$TRAVIS_BRANCH".x-dev; fi; - if [ "$TRAVIS_BRANCH" = "master" ]; then export COMPOSER_ROOT_VERSION=dev-master; else export COMPOSER_ROOT_VERSION="$TRAVIS_BRANCH".x-dev; fi;
install: install:
- if [ "$components" = "no" ]; then composer --prefer-source --dev install; fi; - if [ "$components" = "no" ]; then composer --prefer-source install; fi;
script: script:
- if [ "$components" = "no" ]; then ls -d src/Symfony/*/* | parallel --gnu --keep-order 'echo -e "\\nRunning {} tests"; phpunit --exclude-group tty,benchmark,intl-data {} || (echo -e "\\e[41mKO\\e[0m {}" && $(exit 1));'; fi; - if [ "$components" = "no" ]; then ls -d src/Symfony/*/* | parallel --gnu --keep-order 'echo -e "\\nRunning {} tests"; phpunit --exclude-group tty,benchmark,intl-data {} || (echo -e "\\e[41mKO\\e[0m {}" && $(exit 1));'; fi;
- if [ "$components" = "no" ]; then echo -e "\\nRunning tests requiring tty"; phpunit --group tty || (echo -e "\\e[41mKO\\e[0m tty group" && $(exit 1)); fi; - if [ "$components" = "no" ]; then echo -e "\\nRunning tests requiring tty"; phpunit --group tty || (echo -e "\\e[41mKO\\e[0m tty group" && $(exit 1)); fi;
- if [ "$components" = "high" ]; then find src/Symfony -mindepth 3 -type f -name phpunit.xml.dist | sed 's#\(.*\)/.*#\1#' | parallel --gnu --keep-order -j25% 'echo -e "\\nRunning {} tests"; cd {}; composer --prefer-source --dev update; phpunit --exclude-group tty,benchmark,intl-data || (echo -e "\\e[41mKO\\e[0m {}" && $(exit 1));'; fi; - if [ "$components" = "high" ]; then find src/Symfony -mindepth 3 -type f -name phpunit.xml.dist | sed 's#\(.*\)/.*#\1#' | parallel --gnu --keep-order -j25% 'echo -e "\\nRunning {} tests"; cd {}; composer --prefer-source update; phpunit --exclude-group tty,benchmark,intl-data || (echo -e "\\e[41mKO\\e[0m {}" && $(exit 1));'; fi;
- if [ "$components" = "low" ]; then find src/Symfony -mindepth 3 -type f -name phpunit.xml.dist | sed 's#\(.*\)/.*#\1#' | parallel --gnu --keep-order -j25% 'echo -e "\\nRunning {} tests"; cd {}; composer --prefer-source --dev --prefer-lowest --prefer-stable update; phpunit --exclude-group tty,benchmark,intl-data || (echo -e "\\e[41mKO\\e[0m {}" && $(exit 1));'; fi; - if [ "$components" = "low" ]; then find src/Symfony -mindepth 3 -type f -name phpunit.xml.dist | sed 's#\(.*\)/.*#\1#' | parallel --gnu --keep-order -j25% 'echo -e "\\nRunning {} tests"; cd {}; composer --prefer-source --prefer-lowest --prefer-stable update; phpunit --exclude-group tty,benchmark,intl-data || (echo -e "\\e[41mKO\\e[0m {}" && $(exit 1));'; fi;

View File

@ -10,5 +10,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Bridge/Doctrine/ $ cd path/to/Symfony/Bridge/Doctrine/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -9,5 +9,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Bridge/Monolog/ $ cd path/to/Symfony/Bridge/Monolog/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -9,5 +9,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Bridge/Propel1/ $ cd path/to/Symfony/Bridge/Propel1/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -9,7 +9,7 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Bridge/ProxyManager/ $ cd path/to/Symfony/Bridge/ProxyManager/
$ composer.phar install --dev $ composer install
$ phpunit $ phpunit
[1]: https://github.com/Ocramius/ProxyManager [1]: https://github.com/Ocramius/ProxyManager

View File

@ -11,5 +11,5 @@ If you want to run the unit tests, install dev dependencies before
running PHPUnit: running PHPUnit:
$ cd path/to/Symfony/Bridge/Twig/ $ cd path/to/Symfony/Bridge/Twig/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -19,5 +19,5 @@ provided by the HttpKernel component.
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/BrowserKit/ $ cd path/to/Symfony/Component/BrowserKit/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -81,5 +81,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/ClassLoader/ $ cd path/to/Symfony/Component/ClassLoader/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -12,6 +12,6 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Config/ $ cd path/to/Symfony/Component/Config/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -50,7 +50,7 @@ Tests
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Console/ $ cd path/to/Symfony/Component/Console/
$ composer.phar install $ composer install
$ phpunit $ phpunit
Third Party Third Party

View File

@ -43,5 +43,5 @@ which is distributed under the BSD license.
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/CssSelector/ $ cd path/to/Symfony/Component/CssSelector/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -40,5 +40,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Debug/ $ cd path/to/Symfony/Component/Debug/
$ composer.phar install --dev $ composer install
$ phpunit $ phpunit

View File

@ -77,5 +77,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/DependencyInjection/ $ cd path/to/Symfony/Component/DependencyInjection/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -32,5 +32,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/DomCrawler/ $ cd path/to/Symfony/Component/DomCrawler/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -23,5 +23,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/EventDispatcher/ $ cd path/to/Symfony/Component/EventDispatcher/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -43,5 +43,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Filesystem/ $ cd path/to/Symfony/Component/Filesystem/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -45,7 +45,7 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Finder/ $ cd path/to/Symfony/Component/Finder/
$ composer.phar install $ composer install
$ phpunit $ phpunit
[1]: http://api.symfony.com/2.5/Symfony/Component/Finder/SplFileInfo.html [1]: http://api.symfony.com/2.5/Symfony/Component/Finder/SplFileInfo.html

View File

@ -22,5 +22,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Form/ $ cd path/to/Symfony/Component/Form/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -52,5 +52,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/HttpFoundation/ $ cd path/to/Symfony/Component/HttpFoundation/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -95,5 +95,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/HttpKernel/ $ cd path/to/Symfony/Component/HttpKernel/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -10,7 +10,7 @@ Preparation
To prepare, you need to install the development dependencies of the component. To prepare, you need to install the development dependencies of the component.
$ cd /path/to/Symfony/Component/Intl $ cd /path/to/Symfony/Component/Intl
$ composer.phar install --dev $ composer install
Determining your ICU version Determining your ICU version
--------------------------- ---------------------------

View File

@ -18,7 +18,7 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Intl/ $ cd path/to/Symfony/Component/Intl/
$ composer.phar install --dev $ composer install
$ phpunit $ phpunit
[0]: http://www.php.net/manual/en/intl.setup.php [0]: http://www.php.net/manual/en/intl.setup.php

View File

@ -50,7 +50,7 @@ the subdirectories bin/ and lib/.
For running this script, the intl extension must be loaded and all vendors For running this script, the intl extension must be loaded and all vendors
must have been installed through composer: must have been installed through composer:
composer install --dev composer install
MESSAGE MESSAGE
); );

View File

@ -111,5 +111,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/OptionsResolver/ $ cd path/to/Symfony/Component/OptionsResolver/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -47,5 +47,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Process/ $ cd path/to/Symfony/Component/Process/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -10,5 +10,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/PropertyAccess/ $ cd path/to/Symfony/Component/PropertyAccess/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -32,5 +32,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Routing/ $ cd path/to/Symfony/Component/Routing/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -19,5 +19,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Security/ $ cd path/to/Symfony/Component/Security/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -11,5 +11,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Serializer/ $ cd path/to/Symfony/Component/Serializer/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -9,5 +9,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Stopwatch/ $ cd path/to/Symfony/Component/Stopwatch/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -14,5 +14,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Templating/ $ cd path/to/Symfony/Component/Templating/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -33,5 +33,5 @@ http://symfony.com/doc/2.3/book/translation.html
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Translation/ $ cd path/to/Symfony/Component/Translation/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -122,5 +122,5 @@ http://jcp.org/en/jsr/detail?id=303
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Validator/ $ cd path/to/Symfony/Component/Validator/
$ composer.phar install $ composer install
$ phpunit $ phpunit

View File

@ -17,5 +17,5 @@ Resources
You can run the unit tests with the following command: You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/Yaml/ $ cd path/to/Symfony/Component/Yaml/
$ composer.phar install $ composer install
$ phpunit $ phpunit