Migrate to JHipster v8

[mraible]

According to https://github.com/jhipster/generator-jhipster/issues/23449, JHipster v8 is getting close. We should migrate and make sure everything works correctly.

[asomov]

@sendilkumarn can you please help to identify the work to be done ?

[sendilkumarn]

@asomov I have started working on this branch https://github.com/jhipster/jhipster-kotlin/tree/v8.0.0

There are a quite a few changes in v8

• [ ] Server (WIP @sendilkumarn)
• [ ] Spring Cache
• [ ] Spring Data
• [ ] Spring WebSocket
• [ ] Generator tests
• [ ] Integration Tests
• [ ] Entity Server
• [ ] Entity
• [ ] Generator fixes
• [ ] GitHub actions

Feel free to take any item and work on this branch - https://github.com/jhipster/jhipster-kotlin/tree/v8.0.0

[mshima]

@sendilkumarn do you want some help on this? generator-jhipster v7 -> v8 should be done before any source code change to simplify migration.

[mshima]

Looks like kotlin implementation is identical to generator-jhipster except java files is converted to kt files. Migration plan:

• [x] update cli to match v8 implementation and make ci workflows compatible https://github.com/jhipster/jhipster-kotlin/pull/381.
• [x] improve generator-jhipster templates migration. https://github.com/jhipster/generator-jhipster/pull/26463, https://github.com/jhipster/generator-jhipster/pull/26477
• [x] migrate to v8 using spring-boot v2 templates.

A follow-up task is to update to spring-boot v3 templates.

[asomov]

@mshima is your PR complete? I see a number of different branches in your fork.

[mshima]

@asomov v8 migration using v7 templates is complete. Once merged, there are a few follow-ups.

• Update CI updated cli
• Simplify templates synchronization.
• Merge https://github.com/jhipster/jhipster-kotlin/tree/v8.0.0