Posted by metacello on Feb 17, 2011; 5:49pm
URL: https://forum.world.st/Issue-107-in-metacello-the-toolbox-does-not-recognized-the-default-configuration-tp3309707p3311291.html


Comment #5 on issue 107 by [hidden email]: the toolbox does not  
recognized the #default configuration
http://code.google.com/p/metacello/issues/detail?id=107

Alexandre,

When you use the create* methods, there is an expectation that the project  
is already loaded into your image ... The code will fill in the versions of  
the mcz files and projects that are currently loaded ... if a project or  
mcz file is not loaded it cannot fill in a version...I decided to do use an  
empty version so that it would be obvious that the versions weren't loaded  
rather than default to something that might very well be wrong.

Now if you look at the implementation of  
#createDevelopment:for:importFromBaseline:description:, you will see that  
the #importFrom:... method is called and there are two args updateProjects:  
and updatePackages: that are set to true ... if you pass in false for both  
of those then the versions from the baseline will be used (of course  
baselines don't ususally have versions defined for mcz files)...

As you can see the class-side methods of MetacelloToolBox are a wrapper for  
a much richer api on the instance-side ... so I could add additional  
variants on the basic methods that are present.

When building a literal version from a baseline version, explicit versions  
need to be supplied for the mcz files... somehow, because baseline versions  
don't usually specify them at all ...