[Glass] Seaside 3.1.1 in GemStone 3.1.0.5?

Sat Feb 15 04:14:41 PST 2014

Hi Paul,

The second error is because the ConfigurationOfSeaside3 does not pull in the latest Grease 1.1.
The loading script in the README on the github repo has an explicit step for that. 

I’m busy setting up the Grease port for Gemstone on the glassdb github repository and hope to finish that sometime this weekend.

The first loading error is strange because REST explicitly sets the Core as a prerequisite.
I have updated the configuration baseline and maybe the online version was a bit behind. So it might be fixed now.

Johan

On 14 Feb 2014, at 23:55, Paul DeBruicker <pdebruic at gmail.com> wrote:

> Hey Johan,
> 
> I expect you're already planning to take a look at these but if not I
> noticed a couple other things.  I've reverted back to 3.0.10 because I was
> getting an error when loading 'REST' into gemStone 3.1.0.5.  When loading
> Seaside-REST-Core-JohanBrichau.53 package it complained about needing: 
>  WARequestHandler
>  WARequestFilter
>  WAError
>  WAObject
>  WASystemConfiguration
> 
> So it seems like Seaside-Core.gemstone wasn't loaded. 
> 
> 
> When loading the 'JQuery' group it stumbled on this package:
> Seaside-JSON-Core-DiegoLont.25 and emitted this error:
> 
> a Halt occurred (error 2709), Debug Warning: Warning: This package depends
> on the following classes:
>  GRDelegatingStream
> You must resolve these dependencies before you will be able to load these
> definitions: 
>  GRDelegatingStream>>json:
> 
> 
> 
> 
> I was loading the packages like this:
> 
>  Metacello new
>    baseline: 'Seaside3';
>    repository: 'github://glassdb/Seaside31:gemstone3.1/repository';
>    load: 'REST'
> 
> 
> 
> But the errors also occurred when using my projects configuration.
> 
> 
> Thanks for taking a look
> 
> 
> Paul
> 
> 
> 
> Johan Brichau-3 wrote
>> Hey Paul,
>> 
>> Opening up the ConfigurationOfSeaside3, I think I spotted the problem.
>> Can you load my latest commit and try again?
>> 
>> If it's not working, I will have to dig a bit deeper.
>> 
>> Johan
>> 
>> On 14 Feb 2014, at 21:11, Paul DeBruicker <
> 
>> pdebruic@
> 
>> > wrote:
>> 
>>> Hi Johan,
>>> 
>>> Thanks for the info.  
>>> 
>>> Is there a way to use 3.1.x on GemStone without having to remove the
>>> Seaside
>>> loading instructions on GemStone from all of the Configurations a project
>>> may depend upon?
>>> 
>>> 
>>> If I load Seaside using the github instructions then load my
>>> configuration I
>>> get a conflict error between the Seaside baseline and configuration.
>>> 
>>> 
>>> 
>>> Thanks again
>>> 
>>> Paul
>>> 
>>> 
>>> 
>>> 
>>> Johan Brichau-3 wrote
>>>> Hi Paul,
>>>> 
>>>> In Gemstone, the Seaside-Core package is not loaded. Instead, the
>>>> Gemstone
>>>> port Seaside-Core.gemstone is loaded.
>>>> I added the 3.1.1 version as the #development version but it was not
>>>> (yet)
>>>> intended for Gemstone actually.
>>>> 
>>>> Loading Seaside 3.1 for gemstone now only works using the load
>>>> instructions on github. 
>>>> I'm close to wrapping up the ConfigurationOfSeaside3 though. I will take
>>>> a
>>>> look over the weekend.
>>>> 
>>>> Johan
>>>> 
>>>> On 14 Feb 2014, at 20:45, Paul DeBruicker <
>>> 
>>>> pdebruic@
>>> 
>>>> > wrote:
>>>> 
>>>>> Hello,
>>>>> 
>>>>> Inside my project’s configuration I’m attempting to load Seaside 3.1.1
>>>>> into GemStone 3.1.05 and it fails with this error: 
>>>>> 
>>>>> 
>>>>> ...RETRY->Seaside-Core-pmm.809
>>>>> ...RETRY->Seaside-Core-pmm.809
>>>>> ...FAILED->Seaside-Core-pmm.809
>>>>> 
>>>>> 
>>>>> in the github-cache the metacello version info shows that the ‘version’
>>>>> of Seaside-Core to be pmm.809 so I’m not sure why it can’t find it. 
>>>>> I’ve
>>>>> attached the transcript output from the load.  
>>>>> 
>>>>> 
>>>>> In my configuration I haven’t updated or changed the spec references
>>>>> for
>>>>> Seaside in GemStone. They still point to the ConfigurationOfSeaside3 on
>>>>> smalltalkhub.   I only changed the version from ‘3.0.10’ to ‘3.1.1’. 
>>>>> Should I change it to point to the BaselineOfSeaside3?  If so what is
>>>>> the
>>>>> right way to make that change?  What else should I look at?  
>>>>> 
>>>>> 
>>>>> Things load fine if I follow the instructions on
>>>>> github.com/glassdb/Seaside31 but not if Seaside only a part of the
>>>>> project I’m loading.  
>>>>> 
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> Paul
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>> <seaside31-on-gemstone-3105.rtf>
>>>> _______________________________________________
>>>>> Glass mailing list
>>>>> 
>>> 
>>>> Glass at .gemtalksystems
>>> 
>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>> 
>>>> _______________________________________________
>>>> Glass mailing list
>>> 
>>>> Glass at .gemtalksystems
>>> 
>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> View this message in context:
>>> http://forum.world.st/Glass-Seaside-3-1-1-in-GemStone-3-1-0-5-tp4743869p4743873.html
>>> Sent from the GLASS mailing list archive at Nabble.com.
>>> _______________________________________________
>>> Glass mailing list
>>> 
> 
>> Glass at .gemtalksystems
> 
>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>> 
>> _______________________________________________
>> Glass mailing list
> 
>> Glass at .gemtalksystems
> 
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
> 
> 
> 
> 
> 
> --
> View this message in context: http://forum.world.st/Glass-Seaside-3-1-1-in-GemStone-3-1-0-5-tp4743869p4743897.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140215/9a02bdf9/attachment.html>