On 25/11/11 5:46 PM, Martin Dias wrote:
This can be the problem. Can you update these references to point NewClass?
Now that I know what's holding on to the class, I can figure out what to do. Ideally, I'd like to remove the reference to the class, and have the command list re-generated. This strategy is available for a Pier kernel, but not for the general migration problem for Fuel.
I want to support in fuel 1.8 some way of specifying that a class has been renamed. Something like:
FLMaterializer newDefault classRenames: { #OldClass -> #NewClass } materializeFrom: aFile.
Would this solve your problem?
Yes it would, but the real issue for me is whether or not the migration code stays forever in the code base, or should a one time migration step be run (and keep no migration trail in the Fuel code).