Simple answer: have one module per package and bind only the classes implemented in the corresponding package with each module. Of course there will be exceptions. Then build top-level modules that exist primarily to install your implementation-based modules. For instance you might have a ServerModule that installs the modules that a server depends on. That is the module you'd use to create the Injector. On Aug 19, 2011 2:36 PM, "Efi Merdler" <[email protected]> wrote: > What are the best practices for using modules: > 1. Should I define all my bindings in a single module ? > 2. In case not how would you suggest separating them ? > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/google-guice?hl=en. >
-- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
