There are instructions for loading Seaside 3.0 into GemStone 2.4.4.1, but there are a couple bugs (including #259 and #278) that get in the way when loading Seaside 3.0.5 into GemStone 2.4.4.4. I’ve found that the following Smalltalk code (used in Topaz or a workspace) allows a successful load:
ConfigurationOfGLASS project updateProject. ConfigurationOfGofer project updateProject. ConfigurationOfGoferProjectLoader project updateProject. ConfigurationOfGsCore project updateProject. ConfigurationOfGsMisc project updateProject. ConfigurationOfGsMonticello project updateProject. ConfigurationOfGsOB project updateProject. ConfigurationOfMetacello project updateProject. System commitTransaction. MCPlatformSupport autoMigrate: true. ConfigurationOfMetacello project latestVersion load. ConfigurationOfGoferProjectLoader project load: #stable. MCPlatformSupport autoMigrate: false. System commitTransaction. MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [ [ ConfigurationOfGLASS project load: #stable. ] on: Warning do: [:ex | ex resume ]. ]. System commitTransaction. MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [ [ Gofer project load: 'Seaside30' version: '3.0.5'. ] on: Warning do: [:ex | ex resume ]. ]. System commitTransaction.
Advertisement
1 comment
Comments feed for this article
July 1, 2011 at 4:19 pm
Migrating to Seaside 3.0 « Programming Gems (on GemStone)
[...] how to migrate to a Metacello-based Seaside 2.8. The process involves removing many packages and loading things as if you were in a new repository. Because of the extensive package restructuring and class [...]