Metacello - more on groups

0 views
Skip to first unread message

Dale Henrichs

unread,
May 27, 2009, 1:26:24 PM5/27/09
to montice...@googlegroups.com
After building the examples for Alexandre, I've come to the conclusion, that groups need to be optional.

For Mondrian, the set of packages involved all need to be loaded/manipulated together, so inventing a group name and adding each and every package to that group seems too much like busy work.

The only place that the lack of a group becomes "important" is when another project wants to require Mondrian, but an empty load list (or unspecified load list) is fine:

versionMapSpecForMondrian

^(MetacelloVersionMapSpec for: self)
versionMapClass: 'MondrianVersionMap';
version: '0.1';
loadList: #();
packagesSpec:
((MetacelloPackagesSpec new)
addFile: 'MondrianVersionMap-dkh.3';
addRepository: 'http://seaside.gemstone.com/ss/test';
yourself);

yourself

Dale

Reply all
Reply to author
Forward
0 new messages