If you are using mulitple inheritance to reuse code, you should think twice (even with regular inheritance). Unless there is a meaningful is-a relationship, this is best accomplished via composition.<p>If you are in the Java world, this is where it pays to switch some classes to Groovy and use its @Delegate annotation. It's a compile-time AST transformation, such that straight-up Java code can take advantage, and it can inject the delegated interfaces into its parent class (so now the class can show up as implementing an interface for the dependency injection framework).<p>This can be introduced on an as-needed basis (make some files Groovy and the Java code can call them) and Groovy is essentially 95% compatible with identical Java code, so you can usually rename .java to .groovy and be good to go.