Smalltalk › Frameworks & Tools › Moose

Loading Moose by hand

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

Uko2

Loading Moose by hand

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Andrei Chis

Re: Loading Moose by hand

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 <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev