<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">Phillipe,<br>Could it be that the file library tests are failing because of the configurations' cache of search contexts?<br>I remember hitting a WAAttributeNotFound several times before making it work...<br>
</font></font></font><div style="margin: 2em 0pt;" name="sig_83fa755cf9">Cheers,<br>
Avi.</div><div class="gmail_quote">On Thu, Feb 10, 2011 at 9:00 AM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
2011/2/10 Dale Henrichs <<a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a>>:<br>
<div class="im">> PharoCore1.0:<br>
><br>
> - WAHtmlFileHandlerListingTest>>testFileLibraries results in a<br>
> WAAttributeNotFound being signalled (test error). I'll dig into this<br>
> one a little bit more tomorrow.<br>
> - several WAFileLibraryTests fail the first time tests run, pass<br>
> on rerunning of tests ... I'll ignore these for now<br>
><br>
> PharoCore1.1.1:<br>
><br>
> - several WAFileLibraryTests fail the first time tests run, pass<br>
> on rerunning of tests ... I'll ignore these for now<br>
<br>
</div>That is quite strange. File libraries now do a configuration look up<br>
but when the configuration caches are reset they should pass.<br>
<div class="im"><br>
> Seaside-Core-jf.696:<br>
><br>
> - WABaseElement>>target: is still in the package, so Philippe's edits<br>
> weren't committed (presumably). If the only change that was made at<br>
> the time was to move WABaseElement>>target: from Seaside-Core to<br>
> Seaside-HTML5 then I can do the edit tomorrow (it's getting late<br>
> here:)<br>
> - no other (unexpected) dirty packages<br>
><br>
> Grease-Pharo-Core and WAUrlEncoder:<br>
><br>
> - I'll do these edits tomorrow as well...<br>
><br>
> I also plan on making a pass at loading Seaside3.0 into Pharo1.2 and<br>
> Pharo1.3 according to mail I've seen the only problem with Seaside3.0 on<br>
> Pharo1.2 is related to using the proper version of OB and that's what<br>
> symbolic versions are for, so I should be able to address that issue.<br>
<br>
</div>Besides OB I'm aware of two issues:<br>
- there several deprecation warnings<br>
- file library and tests don't work out of the box because we use<br>
Preferences >> #valueOfFlag: #compileUseNewCompiler:ifAbsent:<br>
<br>
In general it looks like a Grease for Pharo 1.2 is needed.<br>
<br>
Cheers<br>
<font color="#888888">Philippe<br>
</font><div><div></div><div class="h5">_______________________________________________<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" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>