Also note that the bindings configured in the providers are *added* to the aliases map; they don't override the existing keys, but that should be aligned with the current behavior, that already expects more than one namespace URI for a given extension type (see [here](https://github.com/jclouds/jclouds/blob/master/apis/openstack-keystone/src/main/java/org/jclouds/openstack/v2_0/functions/PresentWhenExtensionAnnotationNamespaceEqualsAnyNamespaceInExtensionsSet.java#L63-L69) and [here](https://github.com/jclouds/jclouds/blob/master/apis/openstack-keystone/src/main/java/org/jclouds/openstack/v2_0/predicates/ExtensionPredicates.java#L88)).
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/711#issuecomment-85219694
