JHipster release 3.4.2

What’s new

This is a bug-fix version, and a recommended upgrade for all 3.4.1 users:

  • Fix an important bug making the JavaScript production builds fail #3732
  • Upgrade Spring Cloud to Brixton SR1 #3716

Closed tickets

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:

yo jhipster:upgrade

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:

yo jhipster

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: