Closed mraible closed 4 months ago
npm -g uninstall generator-jhipster
npx -y -- generator-jhipster@8.4.0 upgrade
@mshima I tried your suggestions and they worked. It seems like we need to update our documentation because npx jhipster upgrade
does not work. In this PR, I used the following sequence:
npx jhipster upgrade
, added the changes from package-lock.json, committed and pushednpx -y -- generator-jhipster@8.4.0 upgrade
and pushed the changesIMHO, it seems like it's easier to remember jhipster-migrate
than it is to remember the last command.
One other strange thing I noticed is the build tool prompt has Maven and Gradle in lowercase.
I also noticed that the questions seem to be in a random order compared to 8.1.0. Here are the questions from 8.1.0:
With 8.4.0, many of the client questions are asked first, then the Cypress questions are asked at the end. Having the questions change order between releases makes it hard to write evergreen tutorials about JHipster.
Also, there's a warning about relationships between entities and I haven't created any yet.
@mshima I tried your suggestions and they worked. It seems like we need to update our documentation because
npx jhipster upgrade
does not work. In this PR, I used the following sequence:
- Removed the migrate blueprint from .yo-rc.json and package.json, committed and pushed changes
- Ran
npx jhipster upgrade
, added the changes from package-lock.json, committed and pushed- Ran
npx -y -- generator-jhipster@8.4.0 upgrade
and pushed the changesIMHO, it seems like it's easier to remember
jhipster-migrate
than it is to remember the last command.
Using global installation, they are equivalent: upgrade:
npm install -g generator-jhipster@latest
jhipster upgrade
migrate:
npm install -g generator-jhipster-migrate@latest
jhipster-migrate
npx alternative can be simplified:
npx generator-jhipster@latest upgrade
and a prompt may be asked.I just noticed another typo in the questions. Junit should be JUnit.
Here's a PR to update the instructions: https://github.com/jhipster/jhipster.github.io/pull/1346
With 8.4.0, many of the client questions are asked first, then the Cypress questions are asked at the end. Having the questions change order between releases makes it hard to write evergreen tutorials about JHipster.
We will need a new priority to make every backend generator to configure before client generators.
@mraible is something missing?
The upgrade instructions have been updated and other issues have been fixed, so I'll close this as resolved.
Overview of the issue
I tried to use
npx jhipster upgrade
to upgrade my jhipster8-demo project from 8.3.0 to 8.4.0. I know I could use the migrate blueprint, but I figured it'd be good to test the upgrade instructions.The first time I tried it, the only thing the process changed was the
package-lock.json
file. It did not upgradepackage.json
to use 8.4.0 or modify any other files. I figured this might be caused by existing branches, so I deleted all the branches and tried again. The behavior is the same.Motivation for or Use Case
Our upgrade instructions should work. If
npx jhipster upgrade
is not working, we should recommend the migrate blueprint first.Reproduce the error
Related issues
https://github.com/jhipster/generator-jhipster/issues/25033
Suggest a Fix
Update the documentation to recommend the migrate blueprint, change the
upgrade
command so it works.JHipster Version(s)
JHipster configuration, a
.yo-rc.json
file generated in the root folder.yo-rc.json file
Environment and Tools
openjdk version "17.0.11" 2024-04-16 OpenJDK Runtime Environment Temurin-17.0.11+9 (build 17.0.11+9) OpenJDK 64-Bit Server VM Temurin-17.0.11+9 (build 17.0.11+9, mixed mode)
git version 2.39.3 (Apple Git-146)
node: v20.12.1 npm: 10.7.0
Docker version 26.0.0, build 2ae903e
JDL for the Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryJDL entity definitions