[Seaside] [ANN] Seaside 3.1 and 3.0.10 release
diego.lont at delware.nl
Mon Jan 20 12:28:49 UTC 2014
I am working on GLASS 1.0-beta-9. I do not know how "virgin" this is, I use a build script from Norbert. But reading further: this build script also loads the latest version of Metacello afterwards … and it looks like this version isn't a proper one, as removing this line results in a successful load of Seaside 3.0.9. So it looks like I found the problem. Thank you.
Maybe you can make the latestVersion of Metacello the version of '1.0-beta.32'? Or is there a special reason that "ConfigurationOfMetacello project latestVersion" refers to an older version of Metacello? Because a most configurations bootstrap Metacello using the latest version of Metacello. And since this isn't a version that is able to load seaside, this results in a failure of all Seaside projects, if they have Metacello not preloaded.
On Jan 18, 2014, at 8:32 AM, Johan Brichau wrote:
> Starting from a ‘virgin’ GLASS 1.0-beta-9, when I execute the following snippet. Everything loads fine.
> Gofer new
> url: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> package: 'ConfigurationOfSeaside3';
> ((Smalltalk at: #ConfigurationOfSeaside3) project version: '3.0.9') load
> So, are you on glass 1.0-beta-9 ? Because the version of Metacello that is loaded with that Glass version is working.
> On 17 Jan 2014, at 09:23, Diego Lont <diego.lont at delware.nl> wrote:
>> 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';
>> [ 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?
>> On Jan 4, 2014, at 12:33 PM, Johan Brichau wrote:
>>> You need to load latest Metacello first.
>>> On 03 Jan 2014, at 11:55, Diego Lont <diego.lont at delware.nl> wrote:
>>>> Hi all,
>>>> I am trying to load version 3.0.9 into gemstone, but this fails due to the following error:
>>>> MetacelloVersionConstructor does not understand baseline: with:.
>>>> When I look in my moose image, I can reproduce this error when I try to determine with GTMetaceller what packages to load for Seaside3 for the platform gs.3.x. I do not have any implementers of this message, but I see that the Zinc configuration also uses this construction. Does anyone have a clue why this is added, and why the metaceller gemstone does not understand this?
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside