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')
--groups=Core,Tests,Seaside will do AFAIK :)
would be fine (tests not really being needed).
BTW, stable is not needed right, as it is the default ?
actually true
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â¦
Erwan has set up a Metacello test configuration, we will write some functional tests with it an see how it behaves. After that we can write decent tests for the Configuration command line handler...