[
https://issues.apache.org/jira/browse/JCR-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283366#comment-13283366
]
Randall Hauch commented on JCR-3300:
------------------------------------
Well, we don't *need* it back ported, but we'd prefer it. Of course, it really
depends on the timing of the 2.4.2 release versus the 2.6 release. If they
happen at nearly the same time, then 2.6 is fine.
The reason I asked is that several of the recently reported TCK issues
(JCR-2662, JCR-3307) have already been (recently) applied to the 2.4 branch, so
I was simply hoping that this issue (JCR-3300), JCR-3313 and JCR-2666 can
similarly be applied. I think all three deal with either relaxing some of the
asserts that are too strict or not running tests based upon repository
descriptors, and thus shouldn't affect Jackrabbit's success in passing the TCK,
even on the 2.4 branch.
> 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.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
