Hmm. Perhaps groups are not overridden for separate platforms. You could try defining the 'default' group for each separate platform without defining it for #common. Doru On Thu, Nov 14, 2013 at 3:59 PM, Torsten Bergmann <astares@gmx.de> wrote:

Hi Dale and others:

for the "SimplePersistence" project (see STHub) we need to load a "SimplePersistence-Platform" project right after the core, but only when we run on Pharo 2.0.

The spec looks like this:

baseline301: spec <version: '3.0.1-baseline'>

spec for: #common do: [ spec blessing: #'baseline'. spec description: '- Add Platform package for Pharo 2.0'. spec repository: ' http://smalltalkhub.com/mc/TorstenBergmann/SimplePersistence/main'. spec package: 'SimplePersistence-Core'; package: 'SimplePersistence-Tests' with: [ spec requires: #('SimplePersistence-Core' ). ]. spec group: 'Core' with: #('SimplePersistence-Core' ); group: 'Tests' with: #('SimplePersistence-Tests'); group: 'CI' with: #('Core' 'Tests'); group: 'default' with: #('Core' ) ].

spec for: #'pharo2.x' do: [ spec package: 'SimplePersistence-Platform' with: 'SimplePersistence-Platform.pharo20'. *spec group: 'default' with: #('SimplePersistence-Platform' )* ].

But when I try in a pharo 2.0#20627 image :

Gofer new smalltalkhubUser: 'TorstenBergmann' project: 'SimplePersistence'; package: 'ConfigurationOfSimplePersistence'; load

ConfigurationOfSimplePersistence project development spec inspect

then the 'default' group is not redefined - and the additional platform package for Pharo 2.0 is not loaded.

Any ideas how to achieve that?

Thx T.

-- www.tudorgirba.com "Every thing has its own flow"