Marcelo Shima
Marcelo Shima
> The Micronaut blueprint is currently blocked by [jhipster/generator-jhipster-micronaut#295](https://github.com/jhipster/generator-jhipster-micronaut/pull/295) and the Quarkus blueprint is blocked by [jhipster/generator-jhipster-quarkus#306] I think we should release based on micronaut v3 before moving to v4....
> > I think we should release based on micronaut v3 before moving to v4. > > I'm fine with that. Is there anything we need to do for that...
Yes, but with angular 14 and vue 2.
Release v3.0.0 which uses micronaut 3 and JHipster v8.0.0 - drops support for node v12, v14 and v16. - add support for node v18 and v20 (currently broken) - includes...
I haven’t managed to make the db changelogs to apply. Anyone feel free to take from where I’ve stopped.
@sendilkumarn do you want some help on this? generator-jhipster v7 -> v8 should be done before any source code change to simplify migration.
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...
@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
You can continue from where I’ve started.
https://github.com/mshima/jhipster-lite/tree/jwt You can squash those commits