# path not honored in requirements.yml for 2.1 ?

**URL:** <https://forum.ansible.com/t/path-not-honored-in-requirements-yml-for-2-1/21818>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [June 21, 2016, 3:08am UTC](https://forum.ansible.com/t/path-not-honored-in-requirements-yml-for-2-1/21818 "2016-06-21T03:08:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\
**Post date:** [June 21, 2016, 3:08am UTC](https://forum.ansible.com/t/path-not-honored-in-requirements-yml-for-2-1/21818/1 "2016-06-21T03:08:41Z")

</div>

Our requirements.yml had entries of the form:

`

- src: ansiblebit.oracle-java  
path: vendor/roles/  
name: oracle-java  
`

But how when running galaxy-install these roles are no longer installed in the specified ./vendor/roles directory, but rather into ./roles.

Reading [https://docs.ansible.com/ansible/galaxy.html#roles-path](https://docs.ansible.com/ansible/galaxy.html#roles-path) it says it uses roles\_path, which is defined as:

`  
roles\_path = roles:vendor/roles

`

If I reverse the order then the requirements.yml roles go the correct directory. But still it seems that the path: attribute is being ignored in 2.x.  
I did not read anything about this behavior changing in 2.0. Anybody else running into this?