You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Jeff Potts (JIRA)" <ji...@apache.org> on 2011/03/31 15:50:06 UTC
[jira] [Created] (CMIS-345) Revisit the cmislib version test
Revisit the cmislib version test
--------------------------------
Key: CMIS-345
URL: https://issues.apache.org/jira/browse/CMIS-345
Project: Chemistry
Issue Type: Task
Components: python-cmislib
Reporter: Jeff Potts
The getLatestVersion test in cmislib currently fails for Alfresco because it asserts that the object ID remains unchanged across versions, which is how I interpreted the spec. This task is to validate the intention of the spec, adjust the test if needed, and then re-test against public repositories to validate that it passes in all cases. Where it doesn't pass, issues should be raised against the appropriate back-ends. It probably also makes sense to check the openCMIS versioning logic/tests to see if there are differences with cmislib's implementation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CMIS-345) Revisit the cmislib version test
Posted by "Jeff Potts (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CMIS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Potts resolved CMIS-345.
-----------------------------
Resolution: Not A Problem
Assignee: Jeff Potts
The problem was that Alfresco wasn't spec compliant with regard to this issue. The test now passes for Alfresco 4.0b.
> Revisit the cmislib version test
> --------------------------------
>
> Key: CMIS-345
> URL: https://issues.apache.org/jira/browse/CMIS-345
> Project: Chemistry
> Issue Type: Task
> Components: python-cmislib
> Reporter: Jeff Potts
> Assignee: Jeff Potts
>
> The getLatestVersion test in cmislib currently fails for Alfresco because it asserts that the object ID remains unchanged across versions, which is how I interpreted the spec. This task is to validate the intention of the spec, adjust the test if needed, and then re-test against public repositories to validate that it passes in all cases. Where it doesn't pass, issues should be raised against the appropriate back-ends. It probably also makes sense to check the openCMIS versioning logic/tests to see if there are differences with cmislib's implementation.
--
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