JHipster release 3.7.0
This is a very big release with more than 100 closed tickets and PRs! Here are the most important changes:
- Breaking change if you use i18n, because of #4076. As
translateis an HTML5 element (which is a boolean), we are now using
data-translateinstead. To migrate your application, just do a search and replace from one attribute to the other, in all your HTML files.
- Security issue for people using the Twitter social login, without the rights to use the user’s email address #4024
- Migration to Undertow is our biggest change - see #4054. This brings some very good performance enhancements in start up time and memory usage: this is good for everyone, but people doing microservices will benefit from it even more. With this change, JHipster uses nearly as much JBoss code (Undertow, Hibernate, Bean Validation, MapStruct) as Spring code!
- Upgrade to Gradle 3, which is a huge change for people using Gradle - see #3994
- Support for Feign clients using OAuth2 client - see #3662
- New JHipster DevBox, which now uses the new “Bento” box - see jhipster-devbox/#59
- Upgrade to JHipster Registry v2.5.0, which is an update of the JHipster Registry to use this JHipster v3.7.0 release (with Undertow support, etc)
- Upgrade to JHipster Console v1.3.1 - see JHipster Console v1.3.1 release notes
- Update to Spring Cloud Brixton.SR5 - see #4074 #4094
- Improvements to our Kubernetes sub-generator - see #4049 and #4044
As always, you can check all closed tickets here.
How to upgrade
For an automatic upgrade, starting with JHipster v3.4.0, use the JHipster upgrade sub-generator on an existing application:
For a manual upgrade, first upgrade your version of JHipster with:
npm update -g 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
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