JHipster建筑生产概况

Question

Running Windows 10 platform with the following stack:

• Java 1.8.0_92
• Maven 3.3.9
• JHipster 4.1.0
• Yarn 0.20.3

The application generated is a monolith with AngularJS. Using HTTP Auth - no social plugins.

I am current testing deployment to Heroku and ran into a problem where the deployment simply stops. I have used the following command before with success to deploy more than one app to Heroku:

yo jhipster:heroku

This is preferred method to deploy to Heroku according to the documentation.

Since then I have added PostgreSQL and some entities plus a bit of other code. Running with SpringBoot and yarn locally works 100%. I then tried to deploy to Heroku with the above command, but the process simply hangs. I have tried different options, event upgaded JHipster from 4.0.8 to 4.1.0, regenerating the application from scratch, leaving out all my custom changes...nothing helps.

It seems as if the Maven packaging process is the guilty party here. I then tried to build locally with Maven and the dev profile - success. Changing to prod profile experiences the same process where it just hangs with no response. Both processes stop at the same output.

mvnw package -Pprod -DskipTests

[INFO] --- frontend-maven-plugin:1.3:yarn (webpack build prod) @ test-postgre-sql ---

[INFO] Running 'yarn run webpack:prod' in D:\\DevelopmentProjects\\JHipster\\TestPostgreSQL

[INFO] yarn run v0.21.3

[INFO] $ yarn test && webpack -p --config webpack/webpack.vendor.js && webpack -p --config webpack/webpack.prod.js

That is the last output and the process simply hangs. The Windows resource / performance monitor shows no activity in the network, CPU, memory or disk areas that indicates any activity. Leaving it for 8 hours doesn't help either.

This indicates that the problem exists before the Heroku settings are getting involved.

Any ideas where to start looking for a solution.

Answer 1

Using npm instead of Yarn resolved this problem. From all the tickets logged and questions posted it seems that Yarn is not stable at the moment on the Windows environment. Works with npm.