You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "David Johnson (JIRA)" <ji...@apache.org> on 2009/09/08 04:48:57 UTC
[jira] Updated: (ROL-1815) Media Blogging: migrate old resources to
new system
[ https://issues.apache.org/jira/browse/ROL-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Johnson updated ROL-1815:
-------------------------------
Component/s: (was: Database Access & Data Model)
Media files / uploads
> Media Blogging: migrate old resources to new system
> ---------------------------------------------------
>
> Key: ROL-1815
> URL: https://issues.apache.org/jira/browse/ROL-1815
> Project: Roller
> Issue Type: New Feature
> Components: Media files / uploads
> Reporter: David Johnson
> Assignee: David Johnson
> Priority: Critical
> Fix For: 5.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Must be able to migrate old File Upload resources to new Media File Upload format for 5.0.
> Proposed solution:
> - Use new property names for the media-file storage and resource root URL.
> # The directory in which Roller will upload files
> mediafiles.storage.dir=${user.home}/roller_data/mediafiles
> # The context path under which resoures will be made available
> mediafile.resource.url=/resources
> # Migrate old file resoures to Roller 5.0 Mediafile Storage automatically
> uploads.migrate.auto=true
> - On startup, if Roller finds that the 'uploads.dir' property is set and
> points to a valid directory, then Roller will check the directory for files
> and a migration-status file. If migration status is incomplete, then Roller
> will resume migration until complete.
> * Implemented the "on startup" part in the JPAMediaFileManager.initialize()
> - Migrating a file means copying it from the old 'uploads.dir' to the new
> 'mediafiles.storage.dir' directory, but doing so by using only native Java SE
> file APIs and the new MediaFile manager to do so (i.e. do not depend on the
> old FileManager interface, which will be removed).
>
> (do it via copy so that old URLs still work until FileManager is refactored
> out of existance, see ROL-1816)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.