28 Apr
2015
28 Apr
'15
12:42 a.m.
Hi guys,
do you know, that if one loads Moose by hand in Pharo 4 by running:
Metacello new
smalltalkhubUser: 'Moose'
project: 'Moose';
configuration: 'Moose';
version: #development;
load
then you get a warning:
This package depends on the following classes:
MethodContext
You must resolve these dependencies before you will be able to load these definitions:
classOrMetaClass
messageName
and if you skip it, on any error an emergency evaluator will popup and wont go away.
Uko
28 Apr
28 Apr
12:21 p.m.
So it seems that loading the moose configuration through metacello triggers
that error.
On the ci server we load the configuration package and then do
'ConfigurationOfMoose loadDevelopment.'
Do you know if there is a difference between how configurations are loaded
between the two ways of loading a config?
Cheers,
Andrei
On Tue, Apr 28, 2015 at 12:42 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>
wrote:
Hi guys,
do you know, that if one loads Moose by hand in Pharo 4 by running:
Metacello new
smalltalkhubUser: 'Moose'
project: 'Moose';
configuration: 'Moose';
version: #development;
load
then you get a warning:
This package depends on the following classes:
MethodContext
You must resolve these dependencies before you will be able to load these
definitions:
classOrMetaClass
messageName
and if you skip it, on any error an emergency evaluator will popup and
wont go away.
Uko
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3530
days inactive
3531
days old
1 comments
2 participants
participants (2)
-
Andrei Chis -
Yuriy Tymchuk