Hi,

Just for the record, the jobs are:

Moose 5.1 - loads #stable on top of Pharo 4 https://ci.inria.fr/moose/job/moose-5.1/

Moose 6.0 - loads #development on top of Pharo 5 https://ci.inria.fr/moose/job/moose-6.0/

Cheers, Doru

On Tue, Jun 16, 2015 at 1:37 PM, Andrei Chis chisvasileandrei@gmail.com wrote:

Now we are not using the Moose 5.1 from CI for development. Still I expect the CI job to keep building a working image.

I just tried the latest image from the CI and I see no problem with cmd+g in the Playground. In what pharo image are you loading Moose 5.1?

Cheers, Andrei

On Tue, Jun 16, 2015 at 1:19 PM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:

...

Hi all,

I'm using usually the last MOOSE 5.1 image available in the CI throught Pharo Launcher. Recent MOOSE 5.1 have problems. For example 3 CMD-G in a Playground return a DNU, because String>>findAnySubStr: delimiters startingAt: start has been renamed in Pharo 5.0 into findAnySubStrinhg: delimiters startingAt: start

I guess I should not use these images anymore, but why they are build on the CI ?

The MOOSE 5.1 image should be labelled as stable in Pharo Launcher also.

Regards,

Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev