[Glass] Seaside 3.1.1 in GemStone 3.1.0.5?

[Johan Brichau]

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 at gmail.com> 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 lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass