[Pharo-project] Hudson build for Seaside too?
OK - we have the hudson build for Pharo Core, Pharo, Moose, ... Since Pharo is the reference platform for Seaside wouldnt it make sense to run a hudson build for Seaside too: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. I know that http://hudson.lukas-renggli.ch/ builds a seaside one click ... but still on the old Pharo 1.1. Wouldnt it make sense to have one for Pharo1.2 with Seaside3.0 already. So we can see early when we break things for Seaside ... Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
On 3 February 2011 17:04, Torsten Bergmann <astares@gmx.de> wrote:
OK - we have the hudson build for Pharo Core, Pharo, Moose, ...
Since Pharo is the reference platform for Seaside wouldnt it make sense to run a hudson build for Seaside too:
   Gofer new         squeaksource: 'MetacelloRepository';         package: 'ConfigurationOfSeaside30';     load.
    ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load.
I know that http://hudson.lukas-renggli.ch/ builds a seaside one click ... but still on the old Pharo 1.1.
Wouldnt it make sense to have one for Pharo1.2 with Seaside3.0 already. So we can see early when we break things for Seaside ...
+1
Bye T.
-- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
-- Best regards, Igor Stasenko AKA sig.
+1 Marcus the hudson master :)
OK - we have the hudson build for Pharo Core, Pharo, Moose, ...
Since Pharo is the reference platform for Seaside wouldnt it make sense to run a hudson build for Seaside too:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load.
I know that http://hudson.lukas-renggli.ch/ builds a seaside one click ... but still on the old Pharo 1.1.
Wouldnt it make sense to have one for Pharo1.2 with Seaside3.0 already. So we can see early when we break things for Seaside ...
Bye T.
-- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
On 03 Feb 2011, at 17:04, Torsten Bergmann wrote:
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
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
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
On 3 February 2011 22:08, Dale Henrichs <dhenrich@vmware.com> 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...
I don't know much details, but i think it is possible with metacello to say 'load config which not using OB' . Right?
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
-- Best regards, Igor Stasenko AKA sig.
Yeap, building groups :). On Thu, Feb 3, 2011 at 9:03 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 3 February 2011 22:08, Dale Henrichs <dhenrich@vmware.com> 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...
I don't know much details, but i think it is possible with metacello to say 'load config which not using OB' . Right?
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
-- Best regards, Igor Stasenko AKA sig.
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
participants (6)
-
Dale Henrichs -
Guillermo Polito -
Igor Stasenko -
Stéphane Ducasse -
Sven Van Caekenberghe -
Torsten Bergmann