You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sentry.apache.org by "Gregory Chanan (JIRA)" <ji...@apache.org> on 2013/09/26 05:02:03 UTC

[jira] [Commented] (SENTRY-17) Separate sentry-provider to hive specific and non-specific packages

    [ https://issues.apache.org/jira/browse/SENTRY-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778398#comment-13778398 ] 

Gregory Chanan commented on SENTRY-17:
--------------------------------------

Posted review board request: https://reviews.apache.org/r/14344/
Approach is a little different than the description here, I left the common classes in sentry-provider-file instead of creating a new common package.
                
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira