jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-240) mix:mergeConflict violates naming convention
Date Mon, 13 Aug 2012 15:24:38 GMT

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

angela commented on OAK-240:
----------------------------

since i was dealing with oak-defined node types anyway for the privilege mgt
i can take care of this.
                
> mix:mergeConflict violates naming convention
> --------------------------------------------
>
>                 Key: OAK-240
>                 URL: https://issues.apache.org/jira/browse/OAK-240
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>
> the naming convention for additional node type definitions in jackrabbit
> includes the following rules:
> - never use a reserved prefix/uri defined by the specification
> - node type local name should start with uppercase.
> i would therefore suggest to rename the mixin type defined by oak
> to rep:MergeConflict as long as we don't have a specified, reserved
> namespace definition for oak.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message