Posted by DiegoLont on Jan 17, 2014; 8:23am
URL: https://forum.world.st/ANN-Seaside-3-1-and-3-0-10-release-tp4732637p4737431.html

Hi Johan,

I got side tracked with a few other bugs, but now I really want to fix this problem. I made sure my configuration loads the latest version of Metacello … and still no improvement.

But when I look closer, maybe I do not load the latestVersion … or better said: is the latestVersion not the correct version? I used the template, that is included in all configuration to load Metacello:

        "Bootstrap Gofer (if necessary), bootstrap ConfigurationOfMetacello (using old Gofer API), then load the latest
        version of Metacello itself."
        Smalltalk at: #Gofer ifAbsent: [
                "Current version of Gofer from which to bootstrap - as of 1.0-beta.15"
                self bootstrapPackage: 'Gofer-lr.83' from: 'http://seaside.gemstone.com/ss/metacello' ].
        Smalltalk at: #Gofer ifPresent: [:goferClass | | gofer |
                gofer := goferClass new
                        url: 'http://seaside.gemstone.com/ss/metacello';
                        yourself.
                [ gofer addPackage: 'ConfigurationOfMetacello' ] on: Warning do: [:ex | ex resume ].
                gofer load ].
        "load 'default' group of Metacello"
        (Smalltalk at: #ConfigurationOfMetacello) perform: #load

Does this load the wrong version of Metacello … because I still see a lot of packages that have a more recent version …

Should I load bleeding edge here?

Diego

On Jan 4, 2014, at 12:33 PM, Johan Brichau wrote:

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside