tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity
fba8e2c245
silverstripe-framework/composer.json

101 lines
3.0 KiB
JSON
Raw Normal View History

Added composer.json
2012-11-01 17:28:51 +01:00
{
Fix issues with CMS permission codes Standardise template locations Move CMSSettingsController class to SiteConfig module Fix CMSMenu behaviour for namespaced admin sections Split classes into one per file Manual fixes and cleanup
2016-08-11 01:40:23 +02:00
"name": "silverstripe/framework",
"type": "silverstripe-module",
"description": "The SilverStripe framework",
"homepage": "http://silverstripe.org",
"license": "BSD-3-Clause",
"keywords": ["silverstripe", "framework"],
"authors": [
{
"name": "SilverStripe",
"homepage": "http://silverstripe.com"
},
{
"name": "The SilverStripe Community",
"homepage": "http://silverstripe.org"
}
],
"require": {
"composer/installers": "~1.0",
API Update embed/embed to 3.0 API Better shortcode generation for embed shortcodes
2017-04-03 06:30:01 +02:00
"embed/embed": "^3.0",
PHPParser optimisations and update
2016-05-19 19:50:51 +02:00
"league/flysystem": "~1.0.12",
"monolog/monolog": "~1.11",
"nikic/php-parser": "^2 || ^3",
Only use random_bytes() for RandomGenerator (closes #6397)
2017-05-19 12:18:56 +02:00
"paragonie/random_compat": "^2.0",
PHPParser optimisations and update
2016-05-19 19:50:51 +02:00
"silverstripe/config": "^1@dev",
API Split SilverStripe\Assets into separate module
2017-03-16 04:47:26 +01:00
"silverstripe/assets": "^1@dev",
API Replace i18n message localisation with symfony/translation API Implement enhanced pluralisation Remove Zend_Translate and all Zend dependencies from i18n Deprecated $context from i18n::_t() Warn on missing default string for i18n::_t()
2017-01-18 04:58:48 +01:00
"swiftmailer/swiftmailer": "~5.4",
API Use symfony/cache (fixes #6252)
2017-02-23 20:39:57 +01:00
"symfony/cache": "^3.3@dev",
API Upgrade to behat 3
2017-01-20 03:57:50 +01:00
"symfony/config": "^3.2",
Remove optional Symfony 3.x dependencies They cause issues with installing silverstripe/behat-extension after the fact, since it requires 2.x - and would need the existing project to downgrade the dep. While this should be composer's default behaviour (https://github.com/composer/composer/issues/6121), from a SilverStripe perspective we should have consistent dependencies regardless of the execution path in your require calls - anything else will lead to fragile test vs. prod errors. We can require Symfony 3.x once we've upgraded to Behat 3.x.
2017-02-01 06:09:25 +01:00
"symfony/translation": "^2.8",
API Upgrade to behat 3
2017-01-20 03:57:50 +01:00
"symfony/yaml": "~3.2",
FIX: Add PHP extension requirements to composer. This will raise incompatibilities sooner rather than relying on the installer. GD is excluded from this as it’s a requirement of silverstripe/assets
2017-04-20 07:44:18 +02:00
"vlucas/phpdotenv": "^2.4",
"php": ">=5.6.0",
"ext-intl": "*",
"ext-mbstring": "*",
"ext-xml": "*",
"ext-simplexml": "*",
"ext-dom": "*",
"ext-tokenizer": "*",
"ext-ctype": "*",
"ext-hash": "*",
API PSR-11 compliance (fixes #6594) (#6931) Note that our usage of `$asSingleton` in `get()` is fine. Quote from the PSR: > Two successive calls to get with the same identifier SHOULD return the same value. However, depending on the implementor design and/or user configuration, different values might be returned, so user SHOULD NOT rely on getting the same value on 2 successive calls.
2017-05-19 03:45:07 +02:00
"ext-session": "*",
Require psr/container (#6935) Regression from https://github.com/silverstripe/silverstripe-framework/pull/6931
2017-05-19 06:33:08 +02:00
"psr/container-implementation": "1.0.0",
"psr/container": "1.0.0"
RFC #5487 Remove Oembed in favor of embed/embed. (#5536)
2016-05-27 03:09:03 +02:00
},
Fix issues with CMS permission codes Standardise template locations Move CMSSettingsController class to SiteConfig module Fix CMSMenu behaviour for namespaced admin sections Split classes into one per file Manual fixes and cleanup
2016-08-11 01:40:23 +02:00
"require-dev": {
Package names should be lower case
2017-03-30 16:20:36 +02:00
"phpunit/phpunit": "^5.7",
API Split out SilverStripe\ORM\Versioned into new module
2017-03-21 04:22:23 +01:00
"silverstripe/versioned": "^1.0@dev",
API Upgrade to behat 3
2017-01-20 03:57:50 +01:00
"silverstripe/behat-extension": "^3",
NEW: Move Travis behat test to run locally. This shifts the behat test run to be triggered form composer activity within the framework module directly, * silverstripe/serve is used to provide a webserver, based on the php -S command * se/selenium-server-standalone is used to install selenium rather than a download command Because we’re using serve, the behat configuration can be locked down. Further refinements could be made on this: * the behat-extension could be responsible for installing and starting/stopping selenium, making these tests more portable * xvfb initialisation could be provided with another bin tool in the begat-extension: vendor/bin/xvfb 1024x768 * The bootstrap-file argument to serve could be provided as part of a composer.json setting. This would make it easier for developers to start a dev server simply by running vendor/bin/serve * the behat-extension could be responsible for installing and starting/stopping silverstripe/serve, removing the need for specifying base_url at all, and possibly utilising the same bootstrap file between serve and behat.
2016-09-13 08:23:31 +02:00
"silverstripe/serve": "dev-master",
"se/selenium-server-standalone": "2.41.0"
Fix issues with CMS permission codes Standardise template locations Move CMSSettingsController class to SiteConfig module Fix CMSMenu behaviour for namespaced admin sections Split classes into one per file Manual fixes and cleanup
2016-08-11 01:40:23 +02:00
},
API PSR-11 compliance (fixes #6594) (#6931) Note that our usage of `$asSingleton` in `get()` is fine. Quote from the PSR: > Two successive calls to get with the same identifier SHOULD return the same value. However, depending on the implementor design and/or user configuration, different values might be returned, so user SHOULD NOT rely on getting the same value on 2 successive calls.
2017-05-19 03:45:07 +02:00
"provide": {
"psr/container-implementation": "1.0.0"
},
Fix issues with CMS permission codes Standardise template locations Move CMSSettingsController class to SiteConfig module Fix CMSMenu behaviour for namespaced admin sections Split classes into one per file Manual fixes and cleanup
2016-08-11 01:40:23 +02:00
"extra": {
"branch-alias": {
"dev-master": "4.0.x-dev"
}
},
"autoload": {
"psr-4": {
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\Control\\": "src/Control/",
API Namespace framework tests
2016-10-14 03:30:05 +02:00
"SilverStripe\\Control\\Tests\\": "tests/php/Control/",
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\Core\\": "src/Core/",
API Namespace framework tests
2016-10-14 03:30:05 +02:00
"SilverStripe\\Core\\Tests\\": "tests/php/Core/",
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\Dev\\": "src/Dev/",
API Namespace framework tests
2016-10-14 03:30:05 +02:00
"SilverStripe\\Dev\\Tests\\": "tests/php/Dev/",
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\Forms\\": "src/Forms/",
API Namespace framework tests
2016-10-14 03:30:05 +02:00
"SilverStripe\\Forms\\Tests\\": "tests/php/Forms/",
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\i18n\\": "src/i18n/",
API Namespace framework tests
2016-10-14 03:30:05 +02:00
"SilverStripe\\i18n\\Tests\\": "tests/php/i18n/",
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\Logging\\": "src/Logging/",
API Rename services to match FQN of interface / classes
2017-05-11 07:38:29 +02:00
"SilverStripe\\Logging\\Tests\\": "tests/php/Logging/",
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\ORM\\": "src/ORM/",
API Namespace framework tests
2016-10-14 03:30:05 +02:00
"SilverStripe\\ORM\\Tests\\": "tests/php/ORM/",
NEW: Fixes to allow code files in src/ folder. Separated from the file renames for clarity.
2016-11-01 04:13:06 +01:00
"SilverStripe\\Security\\": "src/Security/",
API Namespace framework tests
2016-10-14 03:30:05 +02:00
"SilverStripe\\Security\\Tests\\": "tests/php/Security/",
"SilverStripe\\View\\": "src/View/",
API Upgrade to behat 3
2017-01-20 03:57:50 +01:00
"SilverStripe\\View\\Tests\\": "tests/php/View/",
"SilverStripe\\Framework\\Tests\\Behaviour\\": "tests/behat/src/"
Fix issues with CMS permission codes Standardise template locations Move CMSSettingsController class to SiteConfig module Fix CMSMenu behaviour for namespaced admin sections Split classes into one per file Manual fixes and cleanup
2016-08-11 01:40:23 +02:00
},
Allow —no-dev install via a PHPUnit shim Partially reinstates the 3.x style PhpUnitWrapper which was removed in d1af214ef5efb817c14b85b639525104d94ef2d9. While we no longer need the full wrapper, the part which creates a fake class is still useful. The preferred alternative would be to remove any references to SapphireTest from non-dev files, which mostly applies to SapphireTest::is_running_test(). This should be solved in a larger refactor of SapphireTest into optional traits and more fine grained functionality.
2017-04-24 01:30:37 +02:00
"files": [
"src/Core/Constants.php",
"src/Dev/PhpUnitShim.php"
API Upgrade to behat 3
2017-01-20 03:57:50 +01:00
]
API Namespace all classes Namespace all templates Move difflib and BBCodeParser2 to thirdparty Remove deprecated API marked for removal in 4.0
2016-08-19 00:51:35 +02:00
},
"include-path": [
NEW: Use composer autoloader to set the right include path.
2016-11-01 03:45:56 +01:00
"src/",
API: Remove TextParser and BBCodeParser These have been archived at https://github.com/silverstripe-archive/silverstripe-bbcodeparser
2016-09-13 22:47:48 +02:00
"thirdparty/"
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released.
2016-09-12 07:42:05 +02:00
],
API Include psr-2 checks in CI
2016-11-28 06:44:19 +01:00
"scripts": {
Add lint-clean and cleanup code linting
2017-05-12 05:17:23 +02:00
"lint": "phpcs src/ tests/php",
"lint-clean": "phpcbf src/ tests/php",
API Enable namespaced-localisation keys in templates BUG Fix whitespaces in SSTemplateParser.peg
2017-04-10 04:11:58 +02:00
"php-peg": "php thirdparty/php-peg/cli.php src/View/SSTemplateParser.peg > src/View/SSTemplateParser.php"
API Include psr-2 checks in CI
2016-11-28 06:44:19 +01:00
},
Update test configuration Note: Retains CMS build
2017-04-04 07:30:02 +02:00
"minimum-stability": "dev",
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released.
2016-09-12 07:42:05 +02:00
"prefer-stable": true
composer/installer dep workaround Moved to end of requirements, to work around a bug in composer - see https://github.com/composer/composer/issues/1147. This caused the dependencies to be installed in the wrong folder because the custom 'silverstripe-module' instructions hadn't been loaded at the time the core modules were installed via composer.
2013-04-30 18:08:50 +02:00
}
Reference in New Issue Copy Permalink