OpenEcoLab-LasAlpujarras
/
farmOS
mirror of https://github.com/farmOS/farmOS.git
3
0
Fork 0
Code Wiki
farmOS/composer.project.json

34 lines
962 B
JSON
Raw Normal View History

Issue #3239420: Use composer-merge-plugin to manage project composer.json dependencies This enables more of the dependencies and configuration that need to be present in the root project composer.json to be managed in the farmOS repository itself, including drupal/core-composer-scaffold and drupal/core-dev, which should match the drupal/core version defined in the farmOS composer.json. Previously these were declared in the project composer.json template in https://github.com/farmOS/composer-project. This configuraton is used as a template when a new farmOS project is created via `composer create-project farmos/project`, but after initial setup it is maintained by the end user. This means that updates to the project composer.json generally requires the end-user to make changes manually. This would be required every time farmOS requires a minor version update of Drupal core. So instead, we can manage those update in this new composer.project.json, and use wikimedia/composer-merge-plugin to merge that into the project composer.json. This allows the project composer.json to be much simpler, and therefore will require less frequent manual updates.
2021-09-24 20:27:21 +02:00
{
"require": {
"cweagans/composer-patches": "^1.7",
Update Drupal core to 10.1.6.
2023-11-01 20:15:46 +01:00
"drupal/core-composer-scaffold": "10.1.6"
Issue #3239420: Use composer-merge-plugin to manage project composer.json dependencies This enables more of the dependencies and configuration that need to be present in the root project composer.json to be managed in the farmOS repository itself, including drupal/core-composer-scaffold and drupal/core-dev, which should match the drupal/core version defined in the farmOS composer.json. Previously these were declared in the project composer.json template in https://github.com/farmOS/composer-project. This configuraton is used as a template when a new farmOS project is created via `composer create-project farmos/project`, but after initial setup it is maintained by the end user. This means that updates to the project composer.json generally requires the end-user to make changes manually. This would be required every time farmOS requires a minor version update of Drupal core. So instead, we can manage those update in this new composer.project.json, and use wikimedia/composer-merge-plugin to merge that into the project composer.json. This allows the project composer.json to be much simpler, and therefore will require less frequent manual updates.
2021-09-24 20:27:21 +02:00
},
"require-dev": {
Explode drupal/core-dev require-dev dependency into the minimum packages we need. The drupal/core-dev package is simply a shortcut for including dependencies necessary for running automated tests. See https://github.com/drupal/core-dev/blob/9.4.x/composer.json It is designed specifically for running Drupal core automated tests. We used it as a simple way to get our automated tests running initially, but it includes some dependencies that we do not need. It also pins some package versions, including symfony/finder and symfony/filesystem. This caused an issue for us when we refactored our composer.json files to use composer-merge-plugin. We got around this issue by pinning symfony/finder to ^4. See https://www.drupal.org/project/farm/issues/3239420 See https://github.com/farmOS/farmOS/commit/bd33d0f139b67d291fa9a4bbf743173f323a767c Furthermore, in testing Drush 11, I discovered that a similar conflict started occurring with symfony/filesystem (presumably because Drush depends on that as well now). I eventually managed to get it to work by pinning symfony/filesystem as well, but only if I moved both pins to the root farmOS composer.json (it didn't fix it if they were in composer.project.json). That is what ultimately drove me to dig into this and decide to split up our dependency on drupal/core-dev. By removing the dependency on drupal/core-dev, we no longer have the issue with symfony/finder, so that pinned dependency can be removed. I repeatedly ran tests with as few of the drupal/core-dev dependencies as possible until tests started passing again. So this final list represents the minimum requirements for our tests.
2022-11-27 17:52:00 +01:00
"behat/mink": "^1.10",
Update drupal/core-dev dependencies.
2023-01-01 22:17:04 +01:00
"behat/mink-browserkit-driver": "^2.1",
Explode drupal/core-dev require-dev dependency into the minimum packages we need. The drupal/core-dev package is simply a shortcut for including dependencies necessary for running automated tests. See https://github.com/drupal/core-dev/blob/9.4.x/composer.json It is designed specifically for running Drupal core automated tests. We used it as a simple way to get our automated tests running initially, but it includes some dependencies that we do not need. It also pins some package versions, including symfony/finder and symfony/filesystem. This caused an issue for us when we refactored our composer.json files to use composer-merge-plugin. We got around this issue by pinning symfony/finder to ^4. See https://www.drupal.org/project/farm/issues/3239420 See https://github.com/farmOS/farmOS/commit/bd33d0f139b67d291fa9a4bbf743173f323a767c Furthermore, in testing Drush 11, I discovered that a similar conflict started occurring with symfony/filesystem (presumably because Drush depends on that as well now). I eventually managed to get it to work by pinning symfony/filesystem as well, but only if I moved both pins to the root farmOS composer.json (it didn't fix it if they were in composer.project.json). That is what ultimately drove me to dig into this and decide to split up our dependency on drupal/core-dev. By removing the dependency on drupal/core-dev, we no longer have the issue with symfony/finder, so that pinned dependency can be removed. I repeatedly ran tests with as few of the drupal/core-dev dependencies as possible until tests started passing again. So this final list represents the minimum requirements for our tests.
2022-11-27 17:52:00 +01:00
"behat/mink-selenium2-driver": "^1.6",
"drupal/coder": "^8.3",
Add PHPStan dependencies: phpstan/phpstan, phpstan/phpstan-deprecation-rules, phpstan/extension-installer, mglaman/phpstan-drupal.
2022-09-12 16:37:10 +02:00
"mglaman/phpstan-drupal": "^1.1",
Explode drupal/core-dev require-dev dependency into the minimum packages we need. The drupal/core-dev package is simply a shortcut for including dependencies necessary for running automated tests. See https://github.com/drupal/core-dev/blob/9.4.x/composer.json It is designed specifically for running Drupal core automated tests. We used it as a simple way to get our automated tests running initially, but it includes some dependencies that we do not need. It also pins some package versions, including symfony/finder and symfony/filesystem. This caused an issue for us when we refactored our composer.json files to use composer-merge-plugin. We got around this issue by pinning symfony/finder to ^4. See https://www.drupal.org/project/farm/issues/3239420 See https://github.com/farmOS/farmOS/commit/bd33d0f139b67d291fa9a4bbf743173f323a767c Furthermore, in testing Drush 11, I discovered that a similar conflict started occurring with symfony/filesystem (presumably because Drush depends on that as well now). I eventually managed to get it to work by pinning symfony/filesystem as well, but only if I moved both pins to the root farmOS composer.json (it didn't fix it if they were in composer.project.json). That is what ultimately drove me to dig into this and decide to split up our dependency on drupal/core-dev. By removing the dependency on drupal/core-dev, we no longer have the issue with symfony/finder, so that pinned dependency can be removed. I repeatedly ran tests with as few of the drupal/core-dev dependencies as possible until tests started passing again. So this final list represents the minimum requirements for our tests.
2022-11-27 17:52:00 +01:00
"mikey179/vfsstream": "^1.6",
Add PHPStan dependencies: phpstan/phpstan, phpstan/phpstan-deprecation-rules, phpstan/extension-installer, mglaman/phpstan-drupal.
2022-09-12 16:37:10 +02:00
"phpstan/extension-installer": "^1.1",
Check PHP 7.4+ compatibility with PHPCompatibility codesniffer extension.
2022-11-12 16:48:27 +01:00
"phpcompatibility/php-compatibility": "^9",
Add PHPStan dependencies: phpstan/phpstan, phpstan/phpstan-deprecation-rules, phpstan/extension-installer, mglaman/phpstan-drupal.
2022-09-12 16:37:10 +02:00
"phpstan/phpstan": "^1.8",
"phpstan/phpstan-deprecation-rules": "^1.0",
Explode drupal/core-dev require-dev dependency into the minimum packages we need. The drupal/core-dev package is simply a shortcut for including dependencies necessary for running automated tests. See https://github.com/drupal/core-dev/blob/9.4.x/composer.json It is designed specifically for running Drupal core automated tests. We used it as a simple way to get our automated tests running initially, but it includes some dependencies that we do not need. It also pins some package versions, including symfony/finder and symfony/filesystem. This caused an issue for us when we refactored our composer.json files to use composer-merge-plugin. We got around this issue by pinning symfony/finder to ^4. See https://www.drupal.org/project/farm/issues/3239420 See https://github.com/farmOS/farmOS/commit/bd33d0f139b67d291fa9a4bbf743173f323a767c Furthermore, in testing Drush 11, I discovered that a similar conflict started occurring with symfony/filesystem (presumably because Drush depends on that as well now). I eventually managed to get it to work by pinning symfony/filesystem as well, but only if I moved both pins to the root farmOS composer.json (it didn't fix it if they were in composer.project.json). That is what ultimately drove me to dig into this and decide to split up our dependency on drupal/core-dev. By removing the dependency on drupal/core-dev, we no longer have the issue with symfony/finder, so that pinned dependency can be removed. I repeatedly ran tests with as few of the drupal/core-dev dependencies as possible until tests started passing again. So this final list represents the minimum requirements for our tests.
2022-11-27 17:52:00 +01:00
"phpunit/phpunit": "^9",
Include symfony/finder in require-dev to fix version pinning issue when using composer-merge-plugin. Resolves: Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-dev[9.2.0-alpha1, ..., 9.2.x-dev] require symfony/finder ^4.4 -> found symfony/finder[v4.4.0-BETA1, ..., 4.4.x-dev] but the package is fixed to v5.3.7 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - Root composer.json requires drupal/core-dev ~9.2.0 -> satisfiable by drupal/core-dev[9.2.0-alpha1, ..., 9.2.x-dev].
2021-09-25 13:38:36 +02:00
"phpspec/prophecy-phpunit": "^2",
Update drupal/core-dev dependencies.
2023-01-01 22:17:04 +01:00
"symfony/phpunit-bridge": "^6.2"
Issue #3239420: Use composer-merge-plugin to manage project composer.json dependencies This enables more of the dependencies and configuration that need to be present in the root project composer.json to be managed in the farmOS repository itself, including drupal/core-composer-scaffold and drupal/core-dev, which should match the drupal/core version defined in the farmOS composer.json. Previously these were declared in the project composer.json template in https://github.com/farmOS/composer-project. This configuraton is used as a template when a new farmOS project is created via `composer create-project farmos/project`, but after initial setup it is maintained by the end user. This means that updates to the project composer.json generally requires the end-user to make changes manually. This would be required every time farmOS requires a minor version update of Drupal core. So instead, we can manage those update in this new composer.project.json, and use wikimedia/composer-merge-plugin to merge that into the project composer.json. This allows the project composer.json to be much simpler, and therefore will require less frequent manual updates.
2021-09-24 20:27:21 +02:00
},
"conflict": {
"drupal/drupal": "*"
},
"extra": {
"composer-exit-on-patch-failure": true,
"drupal-scaffold": {
"locations": {
"web-root": "web/"
}
},
Update Drupal core to 9.2.8 and remove the core patch that was merged upstream. See https://www.drupal.org/project/drupal/issues/3192365
2021-10-07 16:53:26 +02:00
"enable-patching": true
Issue #3239420: Use composer-merge-plugin to manage project composer.json dependencies This enables more of the dependencies and configuration that need to be present in the root project composer.json to be managed in the farmOS repository itself, including drupal/core-composer-scaffold and drupal/core-dev, which should match the drupal/core version defined in the farmOS composer.json. Previously these were declared in the project composer.json template in https://github.com/farmOS/composer-project. This configuraton is used as a template when a new farmOS project is created via `composer create-project farmos/project`, but after initial setup it is maintained by the end user. This means that updates to the project composer.json generally requires the end-user to make changes manually. This would be required every time farmOS requires a minor version update of Drupal core. So instead, we can manage those update in this new composer.project.json, and use wikimedia/composer-merge-plugin to merge that into the project composer.json. This allows the project composer.json to be much simpler, and therefore will require less frequent manual updates.
2021-09-24 20:27:21 +02:00
}
}