[jira] [Commented] (JSPWIKI-814) VersioningFileProvider does migrate original page properties

["Brian Burch (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JSPWIKI-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897662#comment-13897662 ] 

Brian Burch commented on JSPWIKI-814:
-------------------------------------

I am actively working on this problem and hope to have a patch for review this week. I have some new test cases and am working on a code change for VersioningFileProvider, whose logic has proved more complex than I originally 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
>
>   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)