Generator-jhipster: yo jhipster:upgrade failed from 4.2 to 4.3

Created on 23 Apr 2017  ·  9Comments  ·  Source: jhipster/generator-jhipster

Here is the output:

Welcome to the JHipster Upgrade Sub-Generator
This will upgrade your current application codebase to the latest JHipster version
Looking for latest generator-jhipster version...
New generator-jhipster version found: 4.3.0
Git repository detected
Created branch jhipster_upgrade
Cleaned up directory
Installing JHipster 4.2.0 locally
Installed [email protected]
Regenerating app with jhipster 4.2.0...
Successfully regenerated app with jhipster 4.2.0
Committed with message "Generated with JHipster 4.2.0"
Checked out branch "master"
Current code recorded as generated with version 4.2.0
Updating generator-jhipster to 4.3.0 . This might take some time...
Updated generator-jhipster to version 4.3.0
Checked out branch "jhipster_upgrade"
Cleaned up directory
Regenerating app with jhipster 4.3.0...
Successfully regenerated app with jhipster 4.3.0
Committed with message "Generated with JHipster 4.3.0"
Checked out branch "master"
Merging changes back to master...
Merge done!
Installing dependencies, please wait...
Error jhipster:upgrade

ERROR! yarnfailed.

The yo jhipster:info gives the following output:

Welcome to the JHipster Information Sub-Generator

JHipster Version(s)
[email protected] /Users/testuser/Demo/SmartPrice
└── (empty)

JHipster configuration, a .yo-rc.json file generated in the root folder
{
  "generator-jhipster": {
    "promptValues": {
      "packageName": "com.company.smartprice"
    },
    "jhipsterVersion": "4.2.0",
    "baseName": "SmartPrice",
    "packageName": "com.company.smartprice",
    "packageFolder": "com/company/smartprice",
    "serverPort": "8080",
    "authenticationType": "session",
    "hibernateCache": "ehcache",
    "clusteredHttpSession": false,
    "websocket": false,
    "databaseType": "sql",
    "devDatabaseType": "h2Disk",
    "prodDatabaseType": "mysql",
    "searchEngine": false,
    "messageBroker": false,
    "serviceDiscoveryType": false,
    "buildTool": "maven",
    "enableSocialSignIn": false,
    "rememberMeKey": "286e201fdd317cb4c624967b490c25997edc8f0b",
    "clientFramework": "angular2",
    "useSass": false,
    "clientPackageManager": "yarn",
    "applicationType": "monolith",
    "testFrameworks": [],
    "jhiPrefix": "jhi",
    "enableTranslation": false
  }
}
Entity configuration(s) entityName.json files generated in the .jhipster directory

ls: no such file or directory: .jhipster/*.json

Browsers and Operating System

java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

git version 2.11.0 (Apple Git-81)

node: v7.9.0

npm: 4.2.0

bower: 1.8.0

gulp:
[13:30:37] CLI version 1.2.2

yeoman: 1.8.5

yarn: 0.23.2

area upgrade

Most helpful comment

Based on comments on the #5637 closed ticket, I did yarn upgrade and when the error appeared, I committed the yarn.lock and package.json, then ran jhipster upgrade again based on @jmlw solution. After that it worked perfectly, thank you! and thank you for this amazing framework

All 9 comments

You had an error while running Yarn, didn't you have any error message? Anything can happen here: it depends on your configuration, but also it can fail because of an Internet error, etc...

@glxiong I also encountered this error when I upgrade to 4.3.0. Just ignore in and fix any merge conflicts and run the yarn command.

I confirm the issue

This seems to come from yarn.lock, that is forcing to keep older versions of dependencies (like Typescript, in this case). We should do a yarn upgrade, which is totally logical, in fact.

Hi!
I have the same error when i trying to upgrade my jhipster project
Meanwhile how can we upgrade the project ?
regards!

There are instructions to do it manually, you should follow them.
I'm sorry I didn't have the time to inspect this, and we need as much
information and help as possible here.
For example, you could give your version number, logs, etc... Just saying
that it doesn't work isn't making things go forward.

Based on comments on the #5637 closed ticket, I did yarn upgrade and when the error appeared, I committed the yarn.lock and package.json, then ran jhipster upgrade again based on @jmlw solution. After that it worked perfectly, thank you! and thank you for this amazing framework

Thanks a lot for your feedback !

Closed by #5883

Was this page helpful?
0 / 5 - 0 ratings

Related issues

marcelinobadin picture marcelinobadin  ·  3Comments

SudharakaP picture SudharakaP  ·  3Comments

kaidohallik picture kaidohallik  ·  3Comments

SudharakaP picture SudharakaP  ·  3Comments

pascalgrimaud picture pascalgrimaud  ·  4Comments