roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Johnson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ROL-1815) Media Blogging: migrate old resources to new system
Date Sat, 25 Jul 2009 16:50:15 GMT

     [ https://issues.apache.org/jira/browse/ROL-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Johnson updated ROL-1815:
-------------------------------

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


  was:
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
   - mediafiles.storage.dir=${user.home}/roller_data/mediafiles
   - mediafiles.resource.url=/resources

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

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


    Level of effort: Took about a day of dev time

Implementation for Media Blogging: migrate old resources to new system
https://issues.apache.org/jira/browse/ROL-1815

Migration is currently turned off because I'm still testing it and not ready to mark this
resolved.

Includes a test and some test data.


> 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: Database Access & Data Model
>            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.


Mime
View raw message