Hi Paul,<br><br><div class="gmail_quote">On 5 April 2012 17:34, Paul DeBruicker <span dir="ltr"><<a href="mailto:pdebruic@gmail.com">pdebruic@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In the ConfigurationOFZincHTTPCompone<u></u>nts I made yesterday the latest/stable version is 1.5. So the Seaside configuration doesn't load a new version of Zinc and instead relies on whats provided in the Pharo images. Changing the version of Zinc to 1.5 (or better yet #stable) in the Seaside config and reloading Seaside loads the new version of Zinc.<br>
</blockquote><div><br></div><div>Apologies I thought that it was loading #stable - I now see in versions that it's overridden and specifying 1.2 - I've fixed that now.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also- the Seaside builds for Pharo 1.3 on the Pharo CI server are using a ConfigurationOfSeaside30 thats 4 versions old.<br></blockquote><div><br></div><div>Do you know who is responsible for maintaining the versions on the Pharo CI server? From what you're saying it doesn't simply copy from <a href="http://www.squeaksource.com/MetacelloRepository">http://www.squeaksource.com/MetacelloRepository</a>. </div>
<div><br></div><div>Cheers</div><div><br></div><div>Nick</div><div><br></div><div><br></div></div>