Doru, I was just a little bit worried when RC3 was shipped with a #development blessing for 1.0-beta.25, now I have a concrete reason to be worried.
Since 1.0-beta.25 is in #development, the latestVersion of Metacello is 1.0-beta.24.1 and thats the version that gets loaded by #loadLatestVersion... With that said you _have_ exposed a bug in the #loadLatestVersion method: | project | project := self project. project updateProject. project latestversion load When self project is evaluated the latestVersion is 1.0-beta.24.1. After #updateProject is performed, the latestVersion in ConfigurationOfMetacello is 1.0-beta.25.1, but since we don't refresh the project, we load 1.0-beta.24.1. If you do "ConfigurationOfMetacello loadLatestVersion", close the walkback(s) and try "ConfigurationOfMetacello loadLatestVersion" again, you'll be updated correctly. I've checked in a fix for #loadLatestVersion, so if you update the configuration first, then do #loadLatestVersion ... that will work also. Nice catch and I hope that you get better, Dale ----- "Tudor Girba" <[email protected]> wrote: | Hi, | | I took the RC3 dev image and I tried "ConfigurationOfMetacello | loadLatestVersion", but it fails. | | I did not have time to look into this, but this is problematic :). | | Cheers, | Doru | | | -- | www.tudorgirba.com | | "It's not how it is, it is how we see it." | | | _______________________________________________ | Pharo-project mailing list | [email protected] | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
