[ https://issues.apache.org/jira/browse/JCR-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744520#action_12744520
]
Marcel Reutegger commented on JCR-2147:
---------------------------------------
This breaks configuration compatibility. Existing repositories upgraded to 2.0 using one of
the removed classes in their configuration will not start anymore. Is this really intended.
The affected classes (PersistenceManagers moved from core/state to core/persistence and simple
security implementations moved from security to security/simple) have simply been moved to
another package and it seems to me the consequences are quite significant for such a minor
code rearrangement.
I'd rather keep deprecated classes that are used in configuration or build some backward compatibility
code into the configuration classes (rewriting the class attribute value).
opinions?
> Remove deprecated classes in jackrabbit-core
> --------------------------------------------
>
> Key: JCR-2147
> URL: https://issues.apache.org/jira/browse/JCR-2147
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: angela
> Fix For: 2.0.0
>
>
> similar to JCR-2109 i think i would be favorable to get rid of stuff that has been marked
deprecated for 1.x releases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.