Closed mplawley closed 2 years ago
I can confirm this is an issue. I've seen it recently. I believe it happens because the keys are tied to service discovery and they shouldn't be.
I've managed to reproduce, but the error is that spring-cloud(-starter) is been included as dependency, when it should not.
Overview of the issue
Two missing i18n keys are causing
translation-not-found
errors in the admin health page:Motivation for or Use Case
The admin health page should not have translation-not-found errors.
Reproduce the error
jhipster info
output below. Note especially the affirmative response on the generation of the admin UI and on internationalization.translation-not-found
errors as per the screenshot above.Related issues
This is of the
theme:i18n
label category.Suggest a Fix
See my PR: https://github.com/jhipster/generator-jhipster/pull/19489
jhipster info
output:Welcome to JHipster v7.9.2
Welcome to the JHipster Information Sub-Generator
JHipster Version(s)
JHipster configuration, a
.yo-rc.json
file generated in the root folder.yo-rc.json file
JDL for the Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryJDL entity definitions
Environment and Tools
openjdk version "18.0.2" 2022-07-19 OpenJDK Runtime Environment Homebrew (build 18.0.2+0) OpenJDK 64-Bit Server VM Homebrew (build 18.0.2+0, mixed mode, sharing)
git version 2.32.1 (Apple Git-133)
node: v16.16.0
npm: 8.11.0
Docker version 20.10.17, build 100c701
docker-compose version 1.29.2, build 5becea4c
No change to package.json was detected. No package manager install will be executed.
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryNone
Browsers and Operating System
Tested on macOS 12.4 on Chrome Version 104.0.5112.79 (Official Build) (arm64).