[mkurz]

Play Ebean failed to start with Play's evolutions module disabled, e.g. via:

play.modules.disabled += "play.api.db.evolutions.EvolutionsModule"

No implementation for EvolutionsConfig was bound

That's because EbeanDynamicEvolutions required an injected EvolutionsConfig, which only that module binds. (play.evolutions.enabled = false worked, as it keeps the module.)

Now EbeanDynamicEvolutions looks up the EvolutionsConfig from the injector only when generating the evolution scripts, which only happens with the evolutions module enabled. A custom EvolutionsConfig binding still gets respected. The existing public constructor taking an EvolutionsConfig, used e.g. with compile-time DI via EBeanComponents, is kept; the new @Inject constructor takes Play's Injector instead.

Testing

• New EbeanWithoutEvolutionsModuleTest, which fails without this change with the error above.
• The existing evolution script generation tests pass, which now look up the EvolutionsConfig through the injector. MiMa passes.

Backports: #907 (8.x), #909 (7.x)

[mergify]

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.