Add a
onConflict:[:ex | ex allow];
to your load instructions. e.g.
Metacello new
baseline:'Seaside3';
repository: 'github://SeasideSt/Seaside:v3.4.0/repository';
onConflict:[:ex | ex allow];
load.
Metacello new
repository: 'github://pharo-nosql/voyage:1.6/mc';
baseline: 'Voyage';
onConflict:[:ex | ex allow];
load: 'mongo tests'.
If you're always going to load Voyage after Seaside into a fresh image then
you don't need the #onConflict: send in the Seaside load instructions.
Having it in both allows you to load them in either order.
Jan Čada-2 wrote
> Hi,
>
> I am trying to load Seaside and Voyage to Pharo 7.0 64bit image using
> following :
>
> Metacello new
> baseline:'Seaside3';
> repository: 'github://SeasideSt/Seaside:v3.4.0/repository';
> load.
>
> Metacello new
> repository: 'github://pharo-nosql/voyage:1.6/mc';
> baseline: 'Voyage';
> load: 'mongo tests'.
>
>
> I am getting dependency error:
>
> Load Conflict between existing BaselineOfGrease [baseline] from
> github://SeasideSt/Grease:v1.4.x/repository and BaselineOfGrease
> [baseline] from github://SeasideSt/Grease:v1.4.3/repository
> <github://SeasideSt/Grease:v1.4.3/repository>
>
> - to me it seems that both Grease versions are in the end same. I see
> following in transcript:
> Project: Grease Core Tests baseline
> Fetched -> Grease-Tests-Core-CompatibleUserName.1554365153 ---
>
https://github.com/SeasideSt/Grease.git[v1.4.3, v1.4.x] ---
>
https://github.com/SeasideSt/Grease.git[v1.4.x]
> Fetched -> Grease-Tests-Pharo-Core-CompatibleUserName.1554365153 ---
>
https://github.com/SeasideSt/Grease.git[v1.4.3, v1.4.x] ---
>
https://github.com/SeasideSt/Grease.git[v1.4.x]
>
> - I do not insist on Seaside or voyage versions - I just took the latest.
>
> Can you please help me with resolving this issue ?
>
>
> Thanks,
>
> Jan
--
Sent from:
http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Locked
