On 2/8/15 4:06 AM, Sven Van Caekenberghe wrote:
On 08 Feb 2015, at 12:03, Manfred Kröhnert <mkroehnert42@googlemail.com> wrote:
Hello Sven,
On Sun, Feb 8, 2015 at 11:32 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: It is always better to depend on Zinc #stable since it still evolves while Pharo 3 does not.
thanks for your advice. This does mean that I should include the "spec project: 'Zinc-Http' with: [ ..." lines, correct? Yes, I think so, I have
project: 'ZincHTTPComponents' with: [ spec className: 'ConfigurationOfZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents'; loads: #('Core' 'Tests' 'REST' 'AWS') ];
which groups you load it up to you, adding the version is OK I guess (I think it defaults to stable), I think the className is needed because of the odd casing.
But I can't say I am a Metacello expert ...
Sven, for not being a Metacello expert you did a good job. Just two things. If you don't specify a verionString, the default is #bleedingEdge. If you want #stable, then it should be explicitly specified. Secondly, your zinc spec (except for the versionString is correct. With the latest versions of Metacello, you can eliminate the need to specify a className by using configuration: or baseline: in place of project: like so: configuration: 'ZincHTTPComponents' with: [ spec versionString: #stable; repository: 'http://mc.stfx.eu/ZincHTTPComponents'; loads: #('Core' 'Tests' 'REST' 'AWS') ]; Dale