Hi,
Is there a good reason to keep the GinModuleAdapter final ?
I'm struggling to get Gin/Guice code live together. I want to avoid code duplication between Guice and Gin modules.
I have some code that can be ran on both client and server and then I have some that is for GWT clients only. I can not declare the shared modules as a Guice module, since then GIN can not use it.
So I had defined GinModules for the shared components and wanted to use them with Guice through the GinModuleAdapter.
But, I am using annotations to supply the modules to my test code with a custom JUnit runner. But that requires a class literal.
So I need to be able to subclass the adapter class (and just call super( Module )) so that I can have a class literal.
Any ideas on how I can achieve this ? short from copying the GinmoduleAdapter class and removing the final ? For all I care you can make all the methods except the constructor final!
Would it be acceptable that GIN is modified to remove the final ?
David