[Seaside-dev] supported squeak/pharo/gemstone versions?

[Paul DeBruicker]

The Pharo specific portions of Grease aren't being loaded, so the load fails when #greaseInteger is sent to a Character. If its only in my machine that's fine and an even so it is likely an easy fix. 

But I do want to set this up. Both so we have some sight into what's working and not and also to define what we're currently supporting. 

The Inria CI right now it has has Pharo 2&3. I haven't checked into running older Pharo versions or squeak/gemstone on their infrastructure. But I will today. 


On Oct 23, 2013, at 10:10 PM, Johan Brichau <johan at inceptive.be> wrote:

> Hi Paul,
> 
> I am building Seaside on 1.4 every night but have no troubles.
> What is the error?
> 
> Johan
> 
>> On 24 Oct 2013, at 07:00, Paul DeBruicker <pdebruic at gmail.com> wrote:
>> 
>> Hi - 
>> 
>> Because of changes (I think just to Grease, but am not sure) I can't load Seaside 3.0.8 from either the ConfigurationOfSeaside30 or ConfigurationOfSeaside3 into Pharo 1.3 or Pharo 1.4.  As a result I am going to get travis CI building Grease and then Seaside again and try to figure it out.
>> 
>> Once I get it set up for one version its not much more effort to get it to run for multiple versions.  I think I can use a local copy of Jenkins to pull in new versions of the Configurations from http://squeaksource.com/MetacelloRepository and http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main
>> 
>> What versions of Squeak, Pharo, and GemStone should I test? 
>> 
>> Similarly what versions of Seaside and Grease are still relevant?  
>> 
>> 
>> Thanks
>> 
>> Paul_______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev