Glen just hit this issue yesterday and I think this is the same issue.
Almost certainly this issue is due to ebean-ddl-generator not being in the test classpath.
Background:
As
part of the modularisation of ebean we split out the ddl generation
into a ebean-ddl-generator module. This module is generally only
required for testing purposes (to generate and run ddl for tests). Prior
to the modularisation of ebean this was all bundled into ebean itself.
This generally makes sense because it reduces the size of ebean and the
number of dependencies it requires for runtime (makes all the ddl
related code and dependencies test scope only dependencies which is a
good thing).
Now ebean-ddl-generator is a
dependency of ebean-test - projects that use ebean-test just get
ebean-ddl-generator BUT projects that don't use ebean-test need to now
explicitly add ebean-ddl-generator as a test dependency (when we didn't
need to do that prior).
<dependency>
<groupId>io.ebean</groupId>
<artifactId>ebean-ddl-generator</artifactId>
<version>12.12.0-SNAPSHOT</version>
<scope>test</scope>
</dependency>
Apologies
as this issue is pretty hard to diagnose / spot. I wonder if we can
improve the situation by logging a warning when trying to generate ddl
without the ebean-ddl-generator in the classpath.
But yes, add ebean-ddl-generator as a test scope dependency and it should all run as before.
Cheers, Rob.