Composer: Difference between revisions
From MoodleDocs
David Mudrak (talk | contribs) m (Text replacement - "<code>" to "<syntaxhighlight lang="php">") |
David Mudrak (talk | contribs) m (Text replacement - "</code>" to "</syntaxhighlight>") |
||
| Line 14: | Line 14: | ||
} | } | ||
} | } | ||
</ | </syntaxhighlight> | ||
And then execute | And then execute | ||
<syntaxhighlight lang="php">php composer.phar install</ | <syntaxhighlight lang="php">php composer.phar install</syntaxhighlight> | ||
= How to prepare and submit composer changes = | = How to prepare and submit composer changes = | ||
| Line 26: | Line 26: | ||
# Pre-requisite: Always use the '''lower PHP version supported''' in the branch the changes are happening. So, if a given branch (MOODLE_37_STABLE) works with PHP 7.1, 7.2 and 7.3...all the following steps will be executed using PHP 7.1 (the lower version supported). | # Pre-requisite: Always use the '''lower PHP version supported''' in the branch the changes are happening. So, if a given branch (MOODLE_37_STABLE) works with PHP 7.1, 7.2 and 7.3...all the following steps will be executed using PHP 7.1 (the lower version supported). | ||
# Perform the required changes to the composer.json file. Normally. | # Perform the required changes to the composer.json file. Normally. | ||
# Remove the composer.lock file that is going to be regenerated. <syntaxhighlight lang="php">rm composer.lock</ | # Remove the composer.lock file that is going to be regenerated. <syntaxhighlight lang="php">rm composer.lock</syntaxhighlight> | ||
# Remove completely the vendor directory. <syntaxhighlight lang="php">rm -fr vendor</ | # Remove completely the vendor directory. <syntaxhighlight lang="php">rm -fr vendor</syntaxhighlight> | ||
# Clean all composer caches. <syntaxhighlight lang="php">php composer.phar clearcache</ | # Clean all composer caches. <syntaxhighlight lang="php">php composer.phar clearcache</syntaxhighlight> | ||
# Run <syntaxhighlight lang="php">php composer.phar update</ | # Run <syntaxhighlight lang="php">php composer.phar update</syntaxhighlight>, a new composer.lock will be regenerated. | ||
# Check that the composer.lock file, together with other changes, does include the changes you've performed in the composer.json file. | # Check that the composer.lock file, together with other changes, does include the changes you've performed in the composer.json file. | ||
# Ideally, run both phpunit and behat tests and verify that there isn't any problem, using all the supported PHP versions. | # Ideally, run both phpunit and behat tests and verify that there isn't any problem, using all the supported PHP versions. | ||
Revision as of 13:03, 14 July 2021
Use composer to download moodle code
Composer.json now includes meta information and hence composer can be used to download the moodle code base. You can do it by creating composer.json file with following information
{
"repositories": [
{
"type": "vcs",
"url": "https://github.com/moodle/moodle.git"
}
],
"require": {
"moodle/moodle": "v3.9.0"
}
}
And then execute
php composer.phar install
How to prepare and submit composer changes
There are a number of situations where we need to update the bundled composer.json] in core. When we upgrade, for a given branch, the phpunit or the behat-extension versions... we also have to update the composer.lock file, in order to guarantee that all the tests will run in a stable, verified environment.
As far as there are a number of variables affecting how that lock file will be generated, here there are some standard steps to follow, in order to guarantee that any change to composer will be always applied in the same, standard and verified way.
- Pre-requisite: Always use the lower PHP version supported in the branch the changes are happening. So, if a given branch (MOODLE_37_STABLE) works with PHP 7.1, 7.2 and 7.3...all the following steps will be executed using PHP 7.1 (the lower version supported).
- Perform the required changes to the composer.json file. Normally.
- Remove the composer.lock file that is going to be regenerated.
rm composer.lock
- Remove completely the vendor directory.
rm -fr vendor
- Clean all composer caches.
php composer.phar clearcache
- Run , a new composer.lock will be regenerated.
php composer.phar update
- Check that the composer.lock file, together with other changes, does include the changes you've performed in the composer.json file.
- Ideally, run both phpunit and behat tests and verify that there isn't any problem, using all the supported PHP versions.
- Done, you can send the changes for review, integration and, if everything goes ok, will be applied upstream without problem.
Ciao :-)
