Status: New Owner: ---- CC: stephane...@gmail.com, anquetil...@gmail.com, usman.bh...@gmail.com Labels: Type-Defect Priority-Critical Component-VerveineJ
New issue 728 by tu...@tudorgirba.com: VerveineJ places methods in the wrong classes http://code.google.com/p/moose-technology/issues/detail?id=728
For some reason, some methods are placed in the wrong classes.
I did not manage to identify a standalone case, but it looks like if we have a case like below:
public class A { ... public void m() { ... x() } }
public class B { public void x() { ... } }
public class C { ... }
we sometimes get x as belonging to class C instead of B. The interesting part is that the invocation will go from A::m() to C::x().
This is a critical issue that stops us from using VerveineJ because the information is too unreliable.