Since we change the dependencies of Moose-all and remove some dep to Moose Cook, maybe it's best if EVERY BODY start with a fresh Moose-All install. It could avoid the inconsistency problems we had when extracting Famix2 from Moose-All (although Cook is less tangled with other moose code, so should cause less problems)

On 17 mai 09, at 16:31, Tudor Girba wrote:

Thanks. I moved the Collection methods to CollectionExtensions.

Cheers, Doru

On 17 May 2009, at 16:18, Laval Jannik wrote:

...

Hi Doru,

I have do this yesterday. The 4 methods have been moved in Moose-CookFamix3.

Maybe there is a problem when I have saved changes. So you can move these methods.

Cheers

On 17 mai 09, at 15:58, Tudor Girba wrote:

...

Hi,

We have both a MooseCook and a Moose-Cook. Moose-Cook is the real one, but MooseCook seems to be very light and basically just have helper methods. Is it Ok to move the existing functionality in other packages and remove this one, or are there other use cases?

Cheers, Doru

-- www.tudorgirba.com

"Every successful trip needs a suitable vehicle."

---

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

---

Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr

---

---

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

-- www.tudorgirba.com

"Every thing has its own flow."

---

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

-- Simon