[
https://issues.apache.org/jira/browse/JSPWIKI-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177669#comment-13177669
]
Juan Pablo Santos RodrÃguez commented on JSPWIKI-454:
-----------------------------------------------------
Couldn't be classes added in JSPWIKI-690 extended in order to import a 2.8
repo? If this export/import process becomes part of the installation process,
it would ease the migration scenario (i.e., we would not worry about someone's
editing while the import takes place).
> Export tool
> -----------
>
> Key: JSPWIKI-454
> URL: https://issues.apache.org/jira/browse/JSPWIKI-454
> Project: JSPWiki
> Issue Type: New Feature
> Components: Core & storage
> Reporter: Janne Jalkanen
> Fix For: 2.8.5
>
>
> In order to facilitate the move to a different backend in 3.0, and also
> allowing people the choice of the 3.0 backend provider, we should have an
> export tool which can export the old format repository to the JCR XML export
> format (System View). This will also be useful in 3.0 for people who want to
> have an implementation-independent database dump.
> A couple of requirements:
> * Must run with existing 2.8.x
> * Must have an export functionality in the Admin UI
> * Should have also a simple GUI
> * Should have also a command-line interface
> * Should also export version histories (though there is no standard
> representation defined in JCR, we may have to invent our own.)
> * May have built-in compression (the XML files are bound to be large)
> (For 3.0 it then obviously becomes: add a tool which allows *importing* of
> such XML document.)
--
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
