[
https://issues.apache.org/jira/browse/JCR-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283423#comment-13283423
]
Jukka Zitting commented on JCR-3300:
------------------------------------
> We actually *do* have features that are written per the specification that
> are failing
> several TCK tests because of bugs in the TCK tests themselves.
Do you have fixes for those test cases? It would be great to have them in
jackrabbit-jcr-tests so that they can be easily incorporated to JSR 333.
> If 2.6 is going to be a bit, we really would love to have these issues fixed
> in 2.4.2.
There's no immediate plan for 2.6, but I was thinking of cutting an unstable
2.5.0 release from trunk within the next few days. Will that work for you?
> tests should consistently check for repository support and fail with
> NotExecutableException when the repo does not support the feature
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-3300
> URL: https://issues.apache.org/jira/browse/JCR-3300
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-tests
> Affects Versions: 2.4.1, 2.6
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.4.2, 2.6
>
>
> AbstractVersionTest should check for Repository.OPTION_VERSIONING_SUPPORTED
> and throw NotExecutableException when not set
> RSessionAccessControlTest needs to extend from AbstractAccessControlTest
> instead of AbstractJCRTest
> etc.
--
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
