Module names are not unique so using just module names for dependencies may get the wrong project. Best practices for specifying dependencies is to also specify the project. See http://www.drupal.org/node/2299747.

CommentFileSizeAuthor
#2 ambiguous_dependencies-2799617-2.patch506 bytestrobey

Comments

trobey created an issue. See original summary.

trobey’s picture

trobey commented
Status: Active » Needs review
StatusFileSize
new ambiguous_dependencies-2799617-2.patch506 bytes
gausarts’s picture

gausarts commented
Category: Bug report » Task

Thank you. Please allow some delay to get back on this.

For projects on drupal.org it is recommended that dependencies now include a project name as follows. ... Since the project name is not required this is backward compatible with existing code. There is no effect on module installation or dependency calculation in Drupal core.

ATM, let's mark it a Task for anything "recommended", "deprecated", "discouraged", and alike.

I am just guessing another reason for this change is probably because there were troubled project names different from the module namespace: manual-crop, social-share, etc.

Feel free to change the Category if you don't think so.

  • gausarts committed e7c423e on 8.x-1.x authored by trobey 
    - #2799617 by trobey: Include project namespace for module dependencies.
gausarts’s picture

gausarts commented
Status: Needs review » Fixed

Committed. Thank you for contribution and patience.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.