JHipster release 4.0.3
This is the third patch release for JHipster 4.0.0, with 52 bug fixes and tickets closed.
One big improvement is that you are now able to use the JHipster Registry with a monolith application, in order to use a distributed Hazelcast cache. You can find more information about this on our “Using a cache” documentation.
We have also greatly improved our documentation, so you should find more easily help on common problems, like running
yarn start to have your client-side development server running.
Closed tickets and merged pull requests
How to upgrade
Manual upgrades (works for JHipster 4.x applications)
For a manual upgrade, first upgrade your version of JHipster with:
yarn global upgrade generator-jhipster
If you have an existing project, it will still use the JHipster version with which it was generated.
To upgrade your project, you must first delete its
node_modules folder and then run:
You can also update your project and all its entities by running
yo jhipster --with-entities
You can also update your entities one-by-one by running again the entity sub-generator, for example if your entity is named Foo
yo jhipster:entity Foo
Automatic upgrade only works for JHipster 3.x applications
For an automatic upgrade, use the JHipster upgrade sub-generator on an existing application:
Help and bugs
If you find any issue with this release, don’t hesitate to:
If the issue you have is an urgent bug or security issue, please:
- Contact @jhipster on Twitter