jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] Resolved: (JCR-2834) Make DefaultSecurityManager the default security manager (instead of SimpleSecurityManager)
Date Wed, 08 Dec 2010 10:11:00 GMT

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

Michael Dürig resolved JCR-2834.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0

Applied the patch at revision 1043343

> Make DefaultSecurityManager the default security manager (instead of SimpleSecurityManager)
> -------------------------------------------------------------------------------------------
>
>                 Key: JCR-2834
>                 URL: https://issues.apache.org/jira/browse/JCR-2834
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, jackrabbit-jca
>    Affects Versions: 2.3.0
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>             Fix For: 2.3.0
>
>         Attachments: JCR-2834.patch
>
>
> JCR-2164 made DefaultSecurityManager the default security manager for test runs. However
the repository.xml included in jackrabbit core and the one for cluster tests still refer to
the SimpleSecurityManager. For consistency reasons I think it makes sense to change these
places to DefaultSecurityManager.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message