On 20 February 2013 18:17, stephane ducasse <stephane.ducasse@free.fr> wrote:
Hi christophe
We should clear up this issue. Did you make progress on that front? The answer of dale are not really giving my hope. I do not want to base all our infrastructure
on a tool that we do not know if it will be maintained.
Metacello is perfectly well maintained, and runs on a number of Smalltalks. It broke on Pharo 2.0 because things changed too quickly, too quickly for Dale to keep up. What would be vastly more constructive than implying that Dale has abandoned Metacello would be applying some Pharo effort towards making it work again on 2.0. frank
Stef
On Feb 15, 2013, at 3:09 PM, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
Hi all,
I have issues with Metacello on Pharo 2.0
If I load and run tests for the version used in Pharo1.4, it gives: (ConfigurationOfMetacello project version: '1.0-beta.31.1.4') load: 'Tests'
<Capture dâécran 2013-02-15 à 14.45.15.png>
Metacello packages shipped with Pharo 2.0 are all packages derived from the latest stable Metacello baseline (1.0-beta.31.1.5) except the MetacelloToolBox. If I load and run tests packages with version described in the latest stable Metacello baseline (1.0-beta.31.1.5), i.e. :
Metacello-TestsCore-DaleHenrichs.14 and Metacello-TestsMC-dkh.351,
it gives (Pharo 2.0 #20547): <Capture dâécran 2013-02-15 à 14.55.36.png>
So, it seems there are some problems. Do we use the rigth versions of Metacello packages?
Regards, Christophe.