Avoiding Embedded DataSource vs. Hikari DataSource Conflicts

[cer]

eventuate-micronaut-examples-customers-and-orders/customers-service/build.gradle

Line 49 in 810dd7b

testRuntime.exclude group: "io.micronaut.configuration", module: "micronaut-jdbc-hikari"

src/main uses Hikari DataSource but some tests want to use Embedded DataSource.

Two questions:

• Who defines the Hikari DataSource?
• Why doesn't the Embedded DataSource override it?
• What other options exist in Micronaut (e.g.profiles??) for handling this scenario?

@dartartem

[dartartem]

1 - service, https://github.com/eventuate-examples/eventuate-micronaut-examples-customers-and-orders/blob/master/customers-service/build.gradle#L24

2 - because there were change in eventuate local https://github.com/eventuate-local/eventuate-local/pull/149/files , you said make it similar to spring. Please see thread: [updating-libraries] report 06/17/2020

3 - there is Requires annotation: https://docs.micronaut.io/latest/api/io/micronaut/context/annotation/Requires.html

[cer]

What about annotating the test datasource with https://docs.micronaut.io/latest/api/io/micronaut/context/annotation/Replaces.html?