You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently arquillian only checks type inside canProvide and ignores qualifiers. This is really limiting as we can have multiple resource providers per type.
For example inside arquillian-cube the StandaloneCubeUrlResourceProvider is only meant to handle URLs annotated with @DockerUrl, but its canProvide() will return true for all URLs. This prevents me from creating and using something like a @KubernetesUrl.
So, I think that ideally we should have a more accurate canProvide or we should iterate over all resource providers until we get one that canProvde a non-null result.
The text was updated successfully, but these errors were encountered:
I was thinking about the same lately, but for this we would need to pass "injection point", not the type itself. Requires quite a bit of work, but definitely helpful.
Currently arquillian only checks type inside
canProvide
and ignores qualifiers. This is really limiting as we can have multiple resource providers per type.For example inside arquillian-cube the StandaloneCubeUrlResourceProvider is only meant to handle URLs annotated with
@DockerUrl
, but its canProvide() will return true for all URLs. This prevents me from creating and using something like a@KubernetesUrl
.So, I think that ideally we should have a more accurate canProvide or we should iterate over all resource providers until we get one that
canProvde
a non-null result.The text was updated successfully, but these errors were encountered: