sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Chanan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SENTRY-17) Separate sentry-provider to hive specific and non-specific packages
Date Wed, 02 Oct 2013 19:19:44 GMT

     [ https://issues.apache.org/jira/browse/SENTRY-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gregory Chanan updated SENTRY-17:
---------------------------------

    Attachment: SENTRY17v4.patch

The HowToContribute page (https://cwiki.apache.org/confluence/display/SENTRY/How+to+Contribute)
says to generate patches using --no-prefix.  Perhaps we should discuss on the dev list?

I attached a newly generated patch not using --no-prefix, could you take a look?

> Separate sentry-provider to hive specific and non-specific packages
> -------------------------------------------------------------------
>
>                 Key: SENTRY-17
>                 URL: https://issues.apache.org/jira/browse/SENTRY-17
>             Project: Sentry
>          Issue Type: Sub-task
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>         Attachments: SENTRY17v2.patch, SENTRY-17v3.patch, SENTRY17v4.patch
>
>
> SENTRY-9 suggests moving the GroupMappingService to core.  I'm thinking of just moving
it to a sentry-provider-common package, which will eventually contain what the non-trivial
authorization providers need.  That way core is just really core model/authorizable/action
related code.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message