<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body 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>http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev<br></blockquote></div><br></div></body></html>