jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3434) Revert backwards-incompatible changes to SecurityProviderImpl
Date Tue, 22 Sep 2015 08:11:04 GMT

    [ https://issues.apache.org/jira/browse/OAK-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902202#comment-14902202

angela commented on OAK-3434:

we do have clients and i know for sure of one project that extends the existing security provide.

a part from that: breaking backwards compatibility is IMO _always_ troublesome because we
simply don't know how our exported public APIs are being used and who uses it. i made a huge
effort (and some compromises) to keep oak security as compatible with jackrabbit as possible
and there must be really compelling reasons for breaking compatibility within a minor version
change. that's my personal take but comparing the number of issues in the security area compared
with other parts of oak, i think it is the right choice.

> Revert backwards-incompatible changes to SecurityProviderImpl
> -------------------------------------------------------------
>                 Key: OAK-3434
>                 URL: https://issues.apache.org/jira/browse/OAK-3434
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: security
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>             Fix For: 1.3.7
>         Attachments: OAK-3434-01.patch
> OAK-3201 introduced some backwards-incompatible changes to {{SecurityProviderImpl}}.
It should be investigated if those changes can be reverted to maintain the backwards compatibility
of the {{org.apache.jackrabbit.oak.security}} package.

This message was sent by Atlassian JIRA

View raw message