[
https://issues.apache.org/jira/browse/JCR-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283373#comment-13283373
]
Julian Reschke commented on JCR-3300:
-------------------------------------
Randall, the reason I ask is because I'd like to avoid blindly porting back
things that aren't needed. If we did that, we wouldn't need trunk, right?
The only reason I can think of for backporting TCK fixes is because somebody
tries to run the TCK against something where the tests fail due to the test
problem, which seems to imply running against something which is not Jackrabbit
in the first place. That's of course fine (that's why we have a TCK), but then
why can't you simply run the tests from trunk?
> 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
