このページを改善する

JHipster release v6.7.0 パーマリンク to "JHipster release v6.7.0"

This is the 1st release in 2020, with 206 closed tickets and merged pull requests.

Here are the most significant ones:

Closed tickets and merged pull requests パーマリンク to "Closed tickets and merged pull requests"

As always, you can check all closed tickets and merged pull requests here.

Backward Compatibility Issues パーマリンク to "Backward Compatibility Issues"

  • v6.5.x and beyond

    • MongoDB: PersistentAuditEvent Documents not found after upgrading (#11290).

      • jhipster upgrade will remove @Field("event_id") annotation on PersistentAuditEvent#id domain class.

      • The goal is identifying Documents properly by _id field instead, using Spring Data @Id annotation. But: when querying pre-upgrade stored documents, the query won’t look for event_id, thus those won’t be found.

      • Such specific case should not impact regular applications behaviour.

      • Domain backwards compatibility can be restored by adding @Field(value = "event_id", targetType = FieldType.OBJECT_ID) annotation to PersistentAuditEvent#id in combination with @Id.

How to upgrade パーマリンク to "How to upgrade"

Automatic upgrade

For an automatic upgrade, use the JHipster upgrade sub-generator on an existing application:

Upgrade your version of JHipster:

npm update -g generator-jhipster

And then run the upgrade sub-generator:

jhipster upgrade

Manual upgrades

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:

jhipster

You can also update your project and all its entities by running

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

jhipster entity Foo

Help and bugs パーマリンク to "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: