[
https://issues.apache.org/jira/browse/JCRTCK-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCRTCK-5:
-------------------------------
Fix Version/s: 2.0.1
Merged to the standalone jcr-tests codebase in revision 825069.
> PredefinedNodeTypeTest too strict
> ---------------------------------
>
> Key: JCRTCK-5
> URL: https://issues.apache.org/jira/browse/JCRTCK-5
> Project: Jackrabbit JCR Tests
> Issue Type: Bug
> Reporter: Marcel Reutegger
> Fix For: 2.0.1
>
> Attachments: JCR-2303.patch
>
>
> Description copied from:
> https://jsr-283.dev.java.net/issues/show_bug.cgi?id=808
> This test check whether the standard JCR node types are exposed as defined in
> the
> spec. Some of the checks are too strict because certain aspects of a standard
> node
> type can be implementation variant:
> - 3.7.16.1.2 "Additions to the Hierarchy": additional super types are
> allowed, but
> the test currently fails if a standard node type has more than the specified
> super
> types.
> - 3.7.16.1.4 "Variant Attributes": some metadata mixins defined in JSR 283
> have
> variant OPV settings and protected flags, but the test currently fails if an
> implementation differs from the standard settings/flags.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
