On 2016-10-04 15:36, Julian Reschke wrote:
Hi there,
so last year, in the context of OAK-3265, we changed tests in
NodeLocalNameTest (jackrabbit-jcr-tests, which is the TCK...).
Unfortunately, this happened without a related JIRA ticket in the JCR
project, and thus went into releases without even being mentioned in the
change logs.
Later on, as Jackrabbit itself now behaved differently from what the
tests expect, these tests were marked as failures -- this is JCR-3913,
which is still open and has a fix version of "2.13.4".
Assuming that we agree that the change in the tests was correct
(Thomas?), we probably should document this in JCR-3913 (stating that
the test were broken and are now fixed), keep the tests marked as
failure, and un-schedule this bug (unless somebody wants to quickly
submit a patch for Jackrabbit).
Feedback appreciated,
Julian
OK, so I
- closed JCR-3913 (because the tests were disabled in Oct 2015),
- created and closed JCR-4038 (describing and tracking the change in
jackrabbit-jcr-tests), and
- created JCR-4039, describing the non-compliance of the Jackrabbit
query impl.
Best regards, Julian
