[Seaside-dev] 3.1 on Gemstone

[Johan Brichau]

I added a new baseline (3.1.0.1-baseline) to support loading into Gemstone.
It imports the BaselineOfSeaside3 which is on github. In this way, the loading for Gemstone happens transparently from the ConfigurationOfSeaside3 but the specs for Gemstone are in the github repo.

There are couple of remaining issues to solve.
Once these are fixed, we can mark the 3.1.0 version for gemstone as well.

In the meantime, see [1] for loading instructions.

[1] https://github.com/glassdb/Seaside31 

On 30 Dec 2013, at 21:33, Johan Brichau <johan at inceptive.be> wrote:

> I wrapped something up to load Seaside3.1 for gemstone from github using the ConfigurationOfSeaside3 
> But I found out many things are wrong with the current configuration and especially with respect to the gemstone specs.
> 
> So I’m not going to rush into making all those changes at this hour. I hope to be able to finish things in the next few days.
> 
> If you are really keen on trying Seaside3.1 for Gemstone, just give the load instructions on the glassdb github repo a try!
> 
> cheers
> Johan
> 
> On 30 Dec 2013, at 09:59, Johan Brichau <johan at inceptive.be> wrote:
> 
>> Diego, all,
>> 
>> I started to prefer to github way of collaborating on Smalltalk projects. The pull-request model, associated code review, great versioning and Travis builds are a great way of working together. So, I will reorganize the Seaside31 repository on github to keep the Gemstone code and the Pharo code in separate branches. This will at least support a possible transition of the development to github at a later time if the dev team desires it.
>> 
>> For now, we can keep using SmalltalkHub of course. But since I’m mostly working with Dale on the Gemstone branch, I will keep the code repo of Seaside3.1 on Gemstone.
>> 
>> Will take care of that later today…
>> 
>> Johan
>> 
>> On 30 Dec 2013, at 09:47, Johan Brichau <johan at inceptive.be> wrote:
>> 
>>> Diego,
>>> 
>>> The gemstone part is not finished in the configuration.
>>> Also, all the ported code is still on github [1].
>>> It is also relatively untested. Although the unit tests work, I have been caught up in making the Zinc adaptor work to properly test it.
>>> 
>>> Now that 3.1 has been officially released, I will include the current state of it in the configuration anyway. It should be fine. The only question I ponder on is if we keep the github repository as the main repository for the gemstone version or not.
>>> 
>>> [1] https://github.com/glassdb/Seaside31
>>> 
>>> On 30 Dec 2013, at 09:37, Diego Lont <diego.lont at delware.nl> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> I also have trouble loading Seaside 3.1 on gemstone. The error I get is that Seaside-Gemstone-JSON-Core is missing.
>>>> 
>>>> Does anyone know if this is an error in the configuration, or if this package should be there somewhere?
>>>> 
>>>> Diego
>>>> 
>>>> _______________________________________________
>>>> seaside-dev mailing list
>>>> seaside-dev at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>> 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20131231/aacac5cc/attachment.htm