Warm up methods in dependencies execute concurrently with root object when bound by interfaces

[wfhartford]

The constraints around the concurrent execution of @WarmUp methods don't seem to apply when classes are bound by interface in a module, for example, in the following Module:

class MyModule extends AbstractModule {
  protected void configure() {
    bind(InterfaceOne.class).to(ImplementationOne.class);
    bind(InterfaceTwo.class).to(ImplementationTwo.class);
  }
}

If both implementations have @WarmUp methods, and ImplementationOne depends on ImplementationTwo, the two @WarmUp methods may be executed concurrently.

I've added a unit test which exposes this to my fork, would you like me to create a pull request?

[Randgalt]

Yes, a PR would be awesome. Unfortunately, I haven't had a lot of time to spend on Governator so I don't know when I can get to it personally.

[Randgalt]

#83

[Randgalt]

This will be in the next release. Thank you for the submission.