[Pharo-project] Hudson build for Seaside too?

Stéphane Ducasse stephane.ducasse at inria.fr
Fri Feb 4 07:12:04 CET 2011


Yes this is my impression.
Frameworks independence and modularity are always good to have.

Stef

On Feb 3, 2011, at 10:08 PM, Dale Henrichs wrote:

> Stef,
> 
> The Seaside control panel is built on top of OB. 
> 
> It is entirely possible to deploy a Seaside application without including the Seaside control panel, but you need to know  how to manually configure/start/stop the adaptors. As a result it was decided to include the control panel as part of the default install.
> 
> For the purposes of testing Seaside, one could arrange to load everything but the control panel - I could provide you with a load expression that excluded the control panel.
> 
> As I think about this it probably is a _good_ to test Seaside against Pharo with and without OB on top of a core image, since Seaside is expected to work in both cases...
> 
> Dale
> 
> On Feb 3, 2011, at 12:40 PM, Stéphane Ducasse wrote:
> 
>> I find strange that seaside relies on OB.
>> We should remove this dependency (of course making sure that OB loads is important) but this is another issue.
>> 
>> Stef
>>>>    Gofer new
>>>> 		squeaksource: 'MetacelloRepository';
>>>> 		package: 'ConfigurationOfSeaside30';
>>>> 	load.
>>>> 	
>>>> 	((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load.	
>>> 
>>> For the last couple of weeks, and again this evening I wanted to start using 1.2 as my main image, but that requires Seaside 3, the above still does not work for me:
>>> 
>>> Pharo1.2rc2
>>> Latest update: #12330
>>> 
>>> ConfigurationOfOmnibrowser>>postLoadOBStandard
>>> 
>>> Preferences DNU #enable
>>> 
>>> As long as Seaside does not load, I will have to stick with 1.1.1, even if I really would like to switch...
>>> And I am pretty sure I am not the only one
>>> 
>>> Sven
>>> 
>>> 
>> 
>> 
> 
> 





More information about the Pharo-project mailing list