nothing we can do here until we have a concrete case to investigate.
Close it until it can be reproduced.

In two weeks I will have 13 students using Moose. It would be good to have this issue
sorted out. 

I will certainly not close it :). I reproduced it several times on proprietary case
studies. I will try to create a simpler case, but maybe in the meantime others have
experienced something similar.

Great job.

However, we still have another case of misplaced methods that is still present.

It is different than the one I sent you in that it seems to only involve super calls
(while the other one was related to calls to a different class). Essentially, something
like:

public class A extends SomeClass {
  ...
  public void x() { 
    super.m()
  }
}

leads to m() being placed in an unrelated class B.

I suspect it is the same issue as the one you fixed only present in a different place.
I am not sure if my description is clear enough.

I will try again to reproduce on a smaller case study.

I believe this second case is solved too.

Hmm, I just tried. First, I fixed the shell script (verveinej.sh) to collect the jars
automatically from the lib folder. Then I removed the obsolete jars. 

But, still, if I run the following experiment, I get 575 potentially problematic methods:

- download ArgoUML 0.32 from:
http://argouml-downloads.tigris.org/argouml-0.32/
- parse, load in Moose, and then execute:
(MooseModel root allModels first allMethods select: [:each |
each sourceAnchor isNil and: [
each parentType sourceAnchor notNil and: [
'<Initializer>' ~= each name and: [
each name ~= each parentType name ]]]]) openInMoose


Am I doing something wrong?