Dario,

I hope to take a look at this later today ... I've got a thing or two to wrap up first ...

Dale

Ciao,

i have a development system based on Pharo 7.0.3.

On it the 26 April i do :

Metacello new

baseline:'Seaside3';

repository:'github://SeasideSt/Seaside:develop/repository';

load

It load: Seaside v3.3.3 commit c985986

Metacello new

baseline:'Magritte';

repository:'github://magritte-metamodel/magritte:master/repository';

load

It load Magritte  commit c8a8cd5

and everything seems to work well.

Now i some test to load the same project on Gemstone 3.4.3

The Seaside with:

GsDeployer deploy: [

  Metacello new
    baseline: 'Seaside3';
    repository: 'github://SeasideSt/Seaside:master/repository';
     onLock: [:ex | ex honor];
     load ].

It load: Seaside v3.3.3 commit c985986   ( like above )

The Magritte with:

GsDeployer deploy: [
  Metacello new
    baseline: 'Magritte';
    repository: 'github://Magritte-metamodel/Magritte:master/source';
    onLock: [:ex | ex honor];
    load ].

A this point the system open a dialog with the error:

Could not resolve: Magritte-Merging [Magritte-Merging] in cache github://Magritte-metamodel/Magritte:master/source (4)

and the Seaside project entry is update to v3.2.4  commit 1f39762

Considerations ?

Thanks,

Dario

P.S. Today i do the command to load  Magritte on a new Pharo 7.0.3 image

The system open a dialog with: 

MetacelloConflictingProjectError: Load Conflict between existing BaselineOfGrease [baseline] from github://SeasideSt/Grease:master/repository and BaselineOfGrease [baseline] from github://SeasideSt/Grease:1.3.5/repository

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.list.inf.unibe.ch/listinfo/smallwiki