On 24 Jun 2013, at 14:16, Camillo Bruni <camillobr...@gmail.com> wrote:
> On 2013-06-24, at 13:26, Sven Van Caekenberghe <s...@stfx.eu> wrote: > >> Camillo, >> >> I think you set up the Seaside contrib build. >> >> https://ci.inria.fr/pharo-contribution/job/Seaside/47/PHARO=20,SEASIDE_VERSION=30,VERSION=stable,VM=vm/console >> >> I noticed that it does not contain a Zn adaptor. >> >> Could you please also do a Zn update and an install of the adaptor ? >> >> ./pharo Seaside.image config http://mc.stfx.eu/ZincHTTPComponents/ >> ConfigurationOfZincHTTPComponents --install=stable >> >> ./pharo Seaside.image config http://mc.stfx.eu/ZincHTTPComponents/ >> ConfigurationOfZincHTTPComponents --install=stable --group=Seaside > > both entries? stable and group Seaside separately? Yes, because the Seaside group is special: it is a hack as it does not depend on either Zinc or Seaside, both for technical MC reasons, while it actually should; in a way it just loads one package. If the config handler could load multiple groups, then the equivalent of ConfigurationOfZincHTTPComponents project latestVersion load: #('Core' 'Tests' 'Seaside') would be fine (tests not really being needed). BTW, stable is not needed right, as it is the default ? Maybe, in the future, we could change ConfigurationCommandLineHandler installVersion: aVersionName | metacelloVersion | self inform: 'Installing ', self configurationName, ' ', aVersionName. metacelloVersion := (self metacelloVersion: aVersionName). (self hasOption: 'group') ifTrue: [ metacelloVersion load: (self optionAt: 'group') ] ifFalse: [ metacelloVersion load ]. Smalltalk snapshot: true andQuit: true. with installVersion: aVersionName | metacelloVersion | self inform: 'Installing ', self configurationName, ' ', aVersionName. metacelloVersion := (self metacelloVersion: aVersionName). (self hasOption: 'group') ifTrue: [ metacelloVersion load: ($, split: (self optionAt: 'group')) ] ifFalse: [ metacelloVersion load ]. Smalltalk snapshot: true andQuit: true. It is just so hard to test… >> Then we should have an up to date and working Seaside image, I hope ;-) >> >> BTW, why are the other builds in the matrix empty ? > > Seaside exposes currently a known issue with Opal under 3.0, will be fixed > as soon as Clement and Marcus are back from vacation, so by the end of this > week. > > The 31 Configuration is still buggy I assume / or not in the same location as > the 30, > let me check once the build completed.. OK, no rush, Seaside 3.0.x in Pharo 2.0 is a good start. Sven
