To use 3rd party code right now, we have to include it directly in our repo. That makes updates to it annoying to do as well.
Composer is an increasingly popular tool for project dependency management that auto-downloads stuff for you. We're already looking to use it for getting code into Drupal in the first place, and it lets us not keep duplicate copies of thousands of lines of code in our repo
(reviews needed, tests to be written or run, documentation to be written, etc.)
User interface changes
(new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text)
(API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate)
Original report by [username]
Now that Drupal 8 is bringing in some of the Symfony components, we need a way to manage them. Composer is a PHP package management system which is heavily inspired by npm, and with Packagist, it provides great support for Symfony.
What this means for Drupal.org is having the the packager process composer.json file during the package build process.
drush dl composer
drush composer install
Beta phase evaluation
|Prioritized changes||The main goal of this issue covers many areas reduces the size of the git repo, makes updates easier, improves deployment and maintenance of sites but adding more emphasis on composer.|
|Disruption||If managed correctly there should be minimal disruption. Firstly testbot needs to be updated to do composer install, and this would also need to be done when creating the zip/tarball packages.|
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch no-vendor-1475510-81.patch. Unable to apply patch. See the log in the details link for more information.
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Drupal installation failed.
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch 1475510-94.patch. Unable to apply patch. See the log in the details link for more information.