sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Ma (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SENTRY-1043) Move ProviderBackend from sentry-provider-common to setnry-backend-provider-common
Date Mon, 01 Feb 2016 03:15:40 GMT
Colin Ma created SENTRY-1043:
--------------------------------

             Summary: Move ProviderBackend from sentry-provider-common to setnry-backend-provider-common
                 Key: SENTRY-1043
                 URL: https://issues.apache.org/jira/browse/SENTRY-1043
             Project: Sentry
          Issue Type: Improvement
            Reporter: Colin Ma
            Assignee: Colin Ma


Currently, Sentry has the concept about binding, authorizationProvider, policy, backendProvider.
(order by hierarchy). The lower object shouldn't refer to higher object. But authorizationProvider
and backendProvider are both included in sentry-provider-common. When sentry-policy-common
adds dependency for backendProvider, there will be a circle dependency, because    sentry-provider-common
depends on sentry-policy-common for the authorizationProvider.
The backendProvider should be separated from sentry-provider-common to solve this problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message