- horrible hack to get around potential load issues when MetacelloProjectRegistration>>merge: gets installed before MetacelloProjectRegistration>>versionInfo
- horrible hack (continued) to get around potential load issues when MetacelloProjectRegistry>>registerProjectRegistration: gets installed before MetacelloProjectRegistration>>versionInfo
- remove the previous horrible hack and cross fingers...
- now that I think a bit, this isn't quite the horrible hack it seems ... the load is performed using GsDeployer class>>bulkMigrate: ... so old class versions are to be expected .... so change that to horrible, justifiable hack ...
A MetacelloProjectRegistration CANNOT have both a Configuration and a Baseline registered. The registration reflects the loaded state of the image and that means that if a baseline was used to load the project then the baseline reflects loaded state. If a configuration was used to load the project then the configuration reflects loaded state ... If a configuration was used to load a baseline, then heaven help you:) for the moment...
- inline MetacelloProjectRegistration>>isValid to correct invalid definition ... detecting INVALID registrations
scale back lineup for quick test turnaround
- restoring some more behavior that was lost during the merge ... trying to correct incorrect load situration where a baseline is loaded into image (and therefore should become the primary registration) not only does it not become the primary, but an invalid registration is created to boot!
- once I get my current load problem corrected, run tests ... hopefully some will fail:)