flow: Goal prepare-package hangs in RC7
Description of the bug
The build-process hangs at the goal prepare-package. If we kill node three times it continues until Running npm install then one needs to kill node again. Aftrer that it works flawlessly. Please see the attached log killingnode.txt. Other people have the same problem
We do have a proxy in our company, but it is configured correctly in Java/Maven and we didn’t have any problems until 2019-08-05. The networking department assured me that there were no changes to proxy/firewall/etc.
Just tell me if I can be of any assistence.
Minimal reproducible example
- Starter project
- downloaded today
- version14
- CDI and Java EE
Expected behavior
The project build after typing mvn package
Actual behavior
The build hangs at prepare-package.
Versions
- Vaadin / Flow version 14
- Java version javac 12.0.2
- OS version Windows 10
- Node 10.16.1 (Node 10.16.0 doesn’t wor either.)
- Browser version (if applicable) N/A
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- Use readLine != null instead of lines For process streams use readLine instead of lines as lines may block. Might fix #6181 # Fixes #6483 — committed to vaadin/flow by caalador 5 years ago
- Use readLine != null instead of lines (#6502) For process streams use readLine instead of lines as lines may block. Might address #6181 Fixes #6483 — committed to vaadin/flow by caalador 5 years ago
- Use readLine != null instead of lines (#6502) For process streams use readLine instead of lines as lines may block. Might address #6181 Fixes #6483 (cherry picked from commit 750d5ba45c9124eb42... — committed to vaadin/flow by caalador 5 years ago
- Use readLine != null instead of lines (#6502) For process streams use readLine instead of lines as lines may block. Might address #6181 Fixes #6483 (cherry picked from commit 750d5ba45c9124eb42... — committed to vaadin/flow by caalador 5 years ago
Stefan Apelt found the solution.
NPM makes a version check over the internet on every invocation and ignores it’s proxy setting. One can disabale this check with the environment-variable
NO_UPDATE_NOTIFIER=1.Would it be possible, to include this setting in the maven plug-in to reduce build-time and support people behind corporate proxies?