Add jooq module

[fabienpuissant]

ci test not relevant because need a database up to install with this jooq plugin, cannot test on mssql. Error to connect due to url error.

[pascalgrimaud]

for the CI test, you can create a new dedicated config with what you need to test jooq

Another idea would be to add it to mariadb, it should work: https://github.com/jhipster/jhipster-lite/blob/main/tests-ci/generate.sh#L232-L239

[fabienpuissant]

for the CI test, you can create a new dedicated config with what you need to test jooq

Another idea would be to add it to mariadb, it should work: https://github.com/jhipster/jhipster-lite/blob/main/tests-ci/generate.sh#L232-L239

But the plugin connects to a database to introspect schema and generate classes depending on what tables exists.
Is it possible in the test ci to have a docker container up with a database ready to be connected to ?

[pascalgrimaud]

Here some steps in the GitHub CI:

• we launch the containers here:
  • https://github.com/jhipster/jhipster-lite/blob/main/.github/workflows/github-actions.yml#L484
  • it will use this start_docker_compose.sh script which will launch the appropriate docker-compose file
• after that, we'll start the application here:
  • https://github.com/jhipster/jhipster-lite/blob/main/.github/workflows/github-actions.yml#L490
  • it will at least test the health management. See https://github.com/jhipster/jhipster-lite/blob/main/tests-ci/start.sh#L36

[fabienpuissant]

Here some steps in the GitHub CI:

• we launch the containers here:

  • https://github.com/jhipster/jhipster-lite/blob/main/.github/workflows/github-actions.yml#L484
  • it will use this start_docker_compose.sh script which will launch the appropriate docker-compose file

• after that, we'll start the application here:

  • https://github.com/jhipster/jhipster-lite/blob/main/.github/workflows/github-actions.yml#L490
  • it will at least test the health management. See https://github.com/jhipster/jhipster-lite/blob/main/tests-ci/start.sh#L36

I started to investigate on it but in fact the db needs to be up at compile time not when we start the app, so on step "Test: verify: " Regarding the workflow, I don't think we have this use case and I don't find a proper way to do it

Here an example : https://github.com/fabienpuissant/jhipster-lite/actions/runs/11622943610/job/32369374084