[
https://issues.apache.org/jira/browse/JSPWIKI-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900594#comment-13900594
]
Brian Burch commented on JSPWIKI-814:
-------------------------------------
My test failures were related to TestEngine's handling of combined properties
files. I changed the use of properties within my test class from static to
instance, and most of the failures went away. I created JIRA JSPWIKI-821 to
document the issue and remember that a clean-up would be desirable.
I have attached a new version of the test class, which demonstrates the
originally-reported migration bug with 5 test cases that all fail because the
author property for the first version is not as expected.
> VersioningFileProvider does migrate original page properties
> ------------------------------------------------------------
>
> Key: JSPWIKI-814
> URL: https://issues.apache.org/jira/browse/JSPWIKI-814
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage
> Affects Versions: 2.10
> Environment: ubuntu linux and openjdk 1.7.0_25. mvn test.
> Reporter: Brian Burch
> Priority: Minor
> Labels: features
> Fix For: FutureVersion
>
> Attachments: JSPWIKI-814-patch, JSPWIKI-814-patch-TestEngine
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The default FileSystemProvider maintains two files for each wiki page. e.g.
> MyPage.txt has an associated MyPage.properties, which records the timestanp
> and author of the last change to that page.
> VersioningFileProvider contains logic to "migrate" a wiki page created by
> FileSystemProvider when it is next updated. This migration works properly for
> MyPage.txt, but the new change history for the page in the OLD/ subdirectory
> starts at version 2 and ignores the history available in MyPage.properties.
> Also, the original MyPage.properties remains in "suspended animation", even
> though the migrated page history has been created.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
