Peter,

I don't know what version of Metacello is loaded into Pharo4.0, but if you are using the latest version of Metacello, locks are honored by default and no onConflict: block is needed ... as an aside, there is�� #onWarningLog, so you can do something like:

Metacello new
baseline: 'ProjectBBB';
repository: 'gitfiletree:///projectBBB';
onWarningLog;
load.

to both honor locks and log Warnings to the transcript ...�� if you want to filter known warnings, then you can use #onWarning: ...

Dale


On 07/20/2015 12:04 PM, Peter Uhn��k wrote:
Hi,

I was playing around with metacello because I wanted to ignore warnings with locks...

currently I am doing something like

~~~~~~~~
Metacello new
baseline: 'ProjectAAA';
repository: 'gitfiletree:///path/to/projectAAA';
lock.

Metacello new
baseline: 'ProjectBBB';
repository: 'gitfiletree:///projectBBB';
onConflict: [ :ex | ex allow ];
load.
~~~~~~~~~

This will load both projects via gitfiletree, however it will also generate a lots of lock warnings which I have to manually confirm - this is bad for scripts.

So the docs ( https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandReference.md )

mention onLock: [ :ex | ex honor ], however in Pharo 5.0 there is no such method "honor".

Is this bug?
Should Metacello be updated on Pharo 5.0?
Will this even solve my problems? (Honoring locks while not throwing warnings).

Thanks,
Peter