# Role dependency changes for 1.3/development

**URL:** <https://forum.ansible.com/t/role-dependency-changes-for-1-3-development/13396>\
**Category:** Ansible Project\
**Created:** [August 30, 2013, 6:45pm UTC](https://forum.ansible.com/t/role-dependency-changes-for-1-3-development/13396 "2013-08-30T18:45:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Cammarata1](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@James\_Cammarata1](https://forum.ansible.com/u/James_Cammarata1)\
**Post date:** [August 30, 2013, 6:45pm UTC](https://forum.ansible.com/t/role-dependency-changes-for-1-3-development/13396/1 "2013-08-30T18:45:46Z")

</div>

We’ve made a small modification to the way role dependencies work. Prior to today, if multiple roles listed a common role as their dependent, the tasks in that common role would be executed more than once. The new behavior changes this to a default of NOT allowing duplicate roles to be added this way, which allows the common “diamond” pattern of dependencies to work properly.

To allow a role to be listed as a dependency more than once, simply add the following to the roles `meta/main.yml`:

allow\_duplicates: yes

The documentation regarding role dependencies has been updated to reflect this.

If you have any questions about this change, please let us know!
