Great, Thierrys solution works.
But I think there is still a problem with RGMethodDefinition. We call self compiledMethod on a RGMethodDefintion, the implementation *always* returns the compiled method from the system, if it exists (regardless whether this ring method is active or not).
I think we should either - don't call #compiledMethod on ring definitions - always return nil for not active definitions - for non active definitions: create a compiled method on demand
what do you think?
Returning nil might be good⦠because non-active ones model methods that are not installed and have no compiled method. But then, the problem is that we use non active Ring definitions as a replacement of what was MethodReference⦠so we need to check if that breaks anything. Another thing we need to check is all uses of Ring: e.g. SystemNavigation. Do we need Ring there? In general, we need to do another pass over Ring in the context of the remote development project. Marcus