Hmm, #onWarningLog doesn't exist either. I'm assuming this is the issue https://pharo.fogbugz.com/f/cases/15456/Load-latest-version-of-metacello
There's linked github issue https://github.com/dalehenrich/metacello-work/issues/354 But running the script (in the github issue) fails, because there's no defined spec for FileTree for Pharo 5.0 I'm not knowledgeable in Monticello so I don't know if I can do anything to help besides user testing. Peter On Mon, Jul 20, 2015 at 9:22 PM, Marcus Denker <[email protected]> wrote: > No. There is an issue on the issue tracker. > > If nobody pushes, nothing will happen. > > Marcus > > On 20 Jul 2015, at 21:04, Peter Uhnák <[email protected]> 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 > > >
