You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Created) (JIRA)" <ji...@apache.org> on 2012/01/18 16:30:40 UTC
[jira] [Created] (JCR-3212) add TCK test for Info map of NODE_MOVED
event on node reordering
add TCK test for Info map of NODE_MOVED event on node reordering
----------------------------------------------------------------
Key: JCR-3212
URL: https://issues.apache.org/jira/browse/JCR-3212
Project: Jackrabbit Content Repository
Issue Type: Sub-task
Components: jackrabbit-jcr-tests, observation
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor
Fix For: 2.6
add the TCK test for this problem, and mark this as known test failure for now
--
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
[jira] [Commented] (JCR-3212) add TCK test for Info map of
NODE_MOVED event on node reordering
Posted by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189093#comment-13189093 ]
Jukka Zitting commented on JCR-3212:
------------------------------------
FTR, the relevant commit was in revision 1233069. Jira doesn't see it because the issue referenced in the commit was JCR-3207. I fixed the commit message afterwards with "svn propset --revprop svn:log".
> add TCK test for Info map of NODE_MOVED event on node reordering
> ----------------------------------------------------------------
>
> Key: JCR-3212
> URL: https://issues.apache.org/jira/browse/JCR-3212
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-jcr-tests, observation
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.6
>
>
> add the TCK test for this problem, and mark this as known test failure for now
--
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
[jira] [Resolved] (JCR-3212) add TCK test for Info map of
NODE_MOVED event on node reordering
Posted by "Julian Reschke (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-3212.
---------------------------------
Resolution: Fixed
> add TCK test for Info map of NODE_MOVED event on node reordering
> ----------------------------------------------------------------
>
> Key: JCR-3212
> URL: https://issues.apache.org/jira/browse/JCR-3212
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-jcr-tests, observation
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.6
>
>
> add the TCK test for this problem, and mark this as known test failure for now
--
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
[jira] [Commented] (JCR-3212) add TCK test for Info map of
NODE_MOVED event on node reordering
Posted by "Julian Reschke (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188523#comment-13188523 ]
Julian Reschke commented on JCR-3212:
-------------------------------------
Turns out that we have test cases for these operations in the TCK, see org.apache.jackrabbit.test.api.observation.NodeReorderTest. However, these tests have been written in a way that also causes the incorrect reporting of reorder data in the info map.
I wouldn't want to remove this completely, because then other aspects (ADDED/REMOVED events) wouldn't be tested anymore (once we mark the tests as failing in Jackrabbit). Instead, we could refactor the tests to check REMOVED and ADDED independently from MOVED.
> add TCK test for Info map of NODE_MOVED event on node reordering
> ----------------------------------------------------------------
>
> Key: JCR-3212
> URL: https://issues.apache.org/jira/browse/JCR-3212
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-jcr-tests, observation
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.6
>
>
> add the TCK test for this problem, and mark this as known test failure for now
--
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
[jira] [Updated] (JCR-3212) add TCK test for Info map of NODE_MOVED
event on node reordering
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3212:
-------------------------------
Fix Version/s: (was: 2.6)
2.5
> add TCK test for Info map of NODE_MOVED event on node reordering
> ----------------------------------------------------------------
>
> Key: JCR-3212
> URL: https://issues.apache.org/jira/browse/JCR-3212
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-jcr-tests, observation
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.5
>
>
> add the TCK test for this problem, and mark this as known test failure for now
--
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