Tim Marcus Moore

It sounds to me like a good thing to fix. I'm not sure why it's hardcoded. Thanks for the detailed notes, @dpennell. A pull request would be a great help.

Discussing in https://discuss.lightbend.com/t/mocking-services-in-a-test/1189/4

@arnaud-deprez this is unrelated to the original issue reported here. Cassandra is not compatible with Java versions newer than 8.

@deepakmehra10 this usually happens because Kafka cannot start up, which could happen for various reasons. Please review the Kafka logs for the reason.

@nithincp this isn't the best place to ask for general Kafka help. Try [Stack Overflow](https://stackoverflow.com/questions/tagged/apache-kafka) or the [Kafka Users mailing list](https://lists.apache.org/[email protected]).

Hi @DerekWWestAwesomeDeveloper thanks for looking into this. All of the existing build tool integration lives in https://github.com/lagom/lagom/tree/master/dev

If you create the schema manually (using the [script provided by `akka-persistence-jdbc`](https://github.com/dnvriend/akka-persistence-jdbc/blob/master/src/test/resources/schema/oracle/oracle-schema.sql), Lagom 1.2.2 fails to detect the tables: ``` 2017-02-22 16:44:54,832 [debug] chirp-impl-application-akka.actor.default-dispatcher-3 - c.l.l.i.p.j.SlickProvider - Creating table, executing:...

The `read_side_offsets` table is created successfully, however.

This problem looks similar to #498 in that the current schema is not detected or used correctly, but the current schema detection is database-specific, so it will need to be...

With the schema manually created and `lagom.persistence.jdbc.create-tables.auto = false` (on version `1.2.3-SNAPSHOT` where that setting is fully respected) there are different errors: ``` 2017-02-28 18:16:23,276 [info] chirp-impl-application-akka.actor.default-dispatcher-6 - c.l.l.i.p.c.ClusterStartupTaskActor -...