Use testcontainers maven plugin for the generation of jooq code
It should make compilation easier for newcomers. Close #1140
hey @juherr i think this PR and the changes it introduces are cleaner than the one in #1140. therefore, i am slightly leaning towards this one.
there are failed checks though.
Yes, I wanted some feedbacks before going deeper. I will try to fix the issues.
when the build pipeline and infra-related stuff are updated, we can refactor tests to include testcontainers. nice initiative!
Java 11 builds are failing because the plugin is build against Java 17. As Java 11 support will be dropped in 2 months, maybe we can assume to drop its support at build time (Java 11 can be still the target but build by Java 17)
Java 17 builds are failing because the database was no more ready (as not used at build time). I try to manage the migration before the tests based on your work at d5a661782d926a1c7cf4f4b3c02304ac378ac0e6 The build is ongoing ;) 🤞
@goekay Everything fixed! 🎉
Ping @goekay WDYT?
Ping @goekay WDYT?
pls give me some time. nowadays i am constantly short on time.
With update to Java 17 - Docker file also can be adjusted
@slachiewicz step by step 😉
Ping @goekay
Ping @goekay
Closing this PR due to inactivity. For an alternative approach, please refer to https://github.com/juherr/evolve/pull/21 for an alternative solution