Add support to JDL entities at CI scripts.

[mshima]

JDL entities must be executed after copying .yo-rc.json and before generating the project (jhipster --with-entities).

• Create 11-generate-config.sh and deprecate 11-generate-entities.sh
11-generate-config.sh copy .yo-rc.json, json entities and generates entities from jdl afterwards.

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• jhipster-online was updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[pascalgrimaud]

Using JDL for generating entities is nice, but I'd prefer another approch:

• I'd remove this part for sqlfull
• use another variable: JHI_JDL_NAME
• use another if block:

if [[ "$JHI_ENTITY" == "jdl" && "$JHI_JDL_NAME" != "" ]]; then
    jhipster --no-insight jdl "$JHI_SAMPLES"/jdl-entities/$JHI_JDL_NAME.jdl --json-only
elif

So it will improve our current CI, don't have any impact for daily builds, blueprints, etc.

[mshima]

"$JHI_ENTITY" == "jdl" is used for generating the entire project using jdl, it would make this PR useless.

[mshima]

@pascalgrimaud this PR is to simplify entity test cases like https://github.com/jhipster/generator-jhipster/blob/c058e12ba363b815f28ca5b635413f0a42266644/test-integration/samples/jdl-entities/custom-id.jdl.

With current implementation I would have to create 8 different files instead of 1.

[pascalgrimaud]

So if I understand well, the final idea is to replace all entity json files to JDL, am I correct ?

[mshima]

So if I understand well, the final idea is to replace all entity json files to JDL, am I correct ?

That's an option to consider.
I could generate the files if you prefer to don't mix entity.json and jdl.

[pascalgrimaud]

Yes, I'm fine.
For other blueprints, Daily builds, etc, we just need to keep :

• the old file 11-generate-entities.sh
• all json entities

Then, in main generator-jhipster, we can use JDL now. It would be easier for us to reproduce the failures

[pascalgrimaud]

@mshima : do you need this PR beeing merged to advance on other PR ?
If yes, I'll merge it and we can improve with JDL in another PR

[mshima]

do you need this PR beeing merged to advance on other PR ?

@pascalgrimaud I've create several PRs to reduce the size of PRs and simplify the review and merge process.
It could be merged together or drop test from the other PR.
If this PR is ok I prefer to merge it prior.