<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I added a new baseline (3.1.0.1-baseline) to support loading into Gemstone.<div>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.</div><div><br></div><div>There are couple of remaining issues to solve.</div><div>Once these are fixed, we can mark the 3.1.0 version for gemstone as well.</div><div><br></div><div>In the meantime, see [1] for loading instructions.</div><div><br></div><div>[1] <a href="https://github.com/glassdb/Seaside31">https://github.com/glassdb/Seaside31</a> </div><div><br></div><div><div><div>On 30 Dec 2013, at 21:33, Johan Brichau <<a href="mailto:johan@inceptive.be">johan@inceptive.be</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I wrapped something up to load Seaside3.1 for gemstone from github using the ConfigurationOfSeaside3 <div>But I found out many things are wrong with the current configuration and especially with respect to the gemstone specs.</div><div><br></div><div>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.</div><div><br></div><div>If you are really keen on trying Seaside3.1 for Gemstone, just give the load instructions on the glassdb github repo a try!</div><div><br></div><div>cheers</div><div>Johan</div><div><br><div><div>On 30 Dec 2013, at 09:59, Johan Brichau <<a href="mailto:johan@inceptive.be">johan@inceptive.be</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Diego, all,<div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Will take care of that later today…</div><div><br></div><div>Johan</div><div><br><div><div><div>On 30 Dec 2013, at 09:47, Johan Brichau <<a href="mailto:johan@inceptive.be">johan@inceptive.be</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Diego,<div><br></div><div>The gemstone part is not finished in the configuration.</div><div>Also, all the ported code is still on github [1].</div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>[1] <a href="https://github.com/glassdb/Seaside31">https://github.com/glassdb/Seaside31</a></div><div><br><div><div>On 30 Dec 2013, at 09:37, Diego Lont <<a href="mailto:diego.lont@delware.nl">diego.lont@delware.nl</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi all,<br><br>I also have trouble loading Seaside 3.1 on gemstone. The error I get is that Seaside-Gemstone-JSON-Core is missing.<br><br>Does anyone know if this is an error in the configuration, or if this package should be there somewhere?<br><br>Diego<br><br>_______________________________________________<br>seaside-dev mailing list<br><a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br><a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br></blockquote></div><br></div></div></blockquote></div><br></div></div></div></blockquote></div><br></div></div></blockquote></div><br></div></body></html>