Integration with Composer

I will give this a shot, assign it to myself.

Here is the first patch. To test it out you need to run composer drupal/mobile_detect inside of the project. This will download the mobile_detect library with composer.

In the future, I think we should add the hook_requirements to make sure that this project can not be install unless we have the library. What you guys think about this ?

Here is an example of hook_requirements from the address project.

/**
 * Implements hook_requirements().
 */
function address_requirements($phase) {
  $requirements = [];
  if ($phase == 'install') {
    if (!class_exists('\CommerceGuys\Addressing\Repository\AddressFormatRepository')) {
      $requirements['addressing_library'] = [
        'description' => t('Address requires the commerceguys/addressing library.'),
        'severity' => REQUIREMENT_ERROR,
      ];
    }
  }

  return $requirements;
}

Maybe we should wait until we have a class from #2627514: Create a service to load the Mobile_Detect library and they implement the hook_requirements

The current patch from #3 will save the Mobile_Detect library into a vendor directory inside of the module. My question should we make this available in to the vendor directory or some place else where the code can be reuse just in case ? Similar of what libraries api where we use to add things on sites/all/libraries.

Composer Manager will search out composer.json files in modules and add them to the root composer.json via the merge plugin.

I had the same conversation with @Crell and other people in IRC. I did not that composer manager did that.

@mpdonadio, Do you think we need to add this extra composer information ?

 "replace": {
    "drupal/core": "~8.0"
  },
  "minimum-stability": "dev",
  "prefer-stable": true,
  "extra": {
    "merge-plugin": {
      "include": [
        "core/composer.json"
      ],
      "recurse": false,
      "replace": false,
      "merge-extra": false
    }
  }

I took this code from https://bojanz.wordpress.com/2015/09/18/d8-composer-definitive-intro/

I use the devel composer.json and the address composer.json as an example and re-roll the entire patch with more useful information. Also, I fix the license because I thought that the license was base of the library and it should be base of the project. I can confirm that the patch have been validate if I run
composer validate.

Also, if I install and configure composer_manager and run composer drupal-update it download the library into the root vendor directory.

I do not think none this is need it.

"replace": {
    "drupal/core": "~8.0"
  },
"prefer-stable": true,
  "extra": {
    "merge-plugin": {
      "include": [
        "core/composer.json"
      ],
      "recurse": false,
      "replace": false,
      "merge-extra": false
    }
  }

Removing this ...

"replace": {
    "drupal/core": "~8.0"
  }
,

From #8 patch because is not need it.

I push #9 patch into the 8.x branch. So we can start moving on with other patches that are dependent on this patch.

There does not seem to be like a real example on how to use a composer.json with Drupal 8 on Drupal.org documentation pages. There are little of information all over the place.

I ended up doing couple things with this patch:

• I open another issue in DrupalConsole with more details explanation on how to generate a more complex/useful composer.json at [generate:composer] Composer.json Stand Alone #1417
• In addition, I added this patch as an example at Add a composer.json file

I'm going to leave as "Needs Review" and assigned it to @mpdonadio for one last review just in case you will like to change something.

I have to change the title because ... I do not think this is necessary directly with "Composer Manager" instead to Composer. I have pushed this into the 8.x.2 branch.