[
https://issues.apache.org/jira/browse/JCR-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914144#comment-17914144
]
Konrad Windszus commented on JCR-5127:
--------------------------------------
Unfortunately one cannot use the expanded names everywhere (see OAK-11397 for
some examples), therefore we cannot deprecate. I propose to instead just link
out in the javadoc to the expanded name version and recommend to use it with
JCR API arguments but leave the qualified ones in place (non-deprecated) for
the other use cases.
> Deprecate JcrConstants' constants which have equivalents in the JCR API
> -----------------------------------------------------------------------
>
> Key: JCR-5127
> URL: https://issues.apache.org/jira/browse/JCR-5127
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Minor
>
> Deprecate all constants in
> https://github.com/apache/jackrabbit/blame/trunk/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/JcrConstants.java
> which have equivalents with expanded names contained in the JCR API and
> outline in the deprecate javadoc tag which constant to use instead.
> If there all constants are deprecate also the whole class should be
> deprecated.
> This is a follow-up to JCR-5096.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
