[jira] [Updated] (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:all-tabpanel ]

Brian Burch updated JSPWIKI-814:
--------------------------------

    Attachment: JSPWIKI-814-patch

Improved comments and layout of the VersioningFileProviderTest.testMigration case, and it has been renamed as testMigrationSimple to clarify its purpose.

Two new tests further examine the behaviour of the Versioning migration logic.

NOTE: line 173 (within testMigrationChangesHistory) has been commented-out and marked with a TODO. This allows the test case to succeed under the current VersioningFileProvider. Uncomment this single line to confirm the previous version's author tag has not been assimilated.

Improved setUp and tearDown logic for VersioningFileProviderTest to avoid cached page content poisoning discovered once three migration cases had been implemented.

> 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)