|
发表于 2020-4-8 11:28:09
|
显示全部楼层
F:\O2OA\gzz\O2OA\o2server>npm run build:win
> o2oa@4.0.3763 build:win F:\O2OA\gzz\O2OA
> npm run clear && npm run preperation:win && npm run build_parallel && npm run deploy:win && npm run typeInfor
> o2oa@4.0.3763 clear F:\O2OA\gzz\O2OA
> gulp clear_build
[11:22:43] Using gulpfile F:\O2OA\gzz\O2OA\gulpfile.js
[11:22:43] Starting 'clear_build'...
---------------------------------------------------------------------
. clear old build ...
---------------------------------------------------------------------
[11:22:43] Finished 'clear_build' after 5.58 ms
> o2oa@4.0.3763 preperation:win F:\O2OA\gzz\O2OA
> gulp preperation --e windows
[11:22:48] Using gulpfile F:\O2OA\gzz\O2OA\gulpfile.js
[11:22:48] Starting 'preperation'...
[11:22:48] Starting 'download_commons_and_jvm'...
[11:22:48] begin download commons and jvm
---------------------------------------------------------------------
. Start to download the dependencies needed for compilation ...
---------------------------------------------------------------------
[11:23:07] 'download_commons_and_jvm' errored after 19 s
[11:23:07] Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:205:27)
[11:23:07] 'preperation' errored after 19 s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! o2oa@4.0.3763 preperation:win: `gulp preperation --e windows`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the o2oa@4.0.3763 preperation:win script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\30344\AppData\Roaming\npm-cache\_logs\2020-04-08T03_23_07_440Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! o2oa@4.0.3763 build:win: `npm run clear && npm run preperation:win && npm run build_parallel && npm run deploy:win && npm run typeInfor`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the o2oa@4.0.3763 build:win script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\30344\AppData\Roaming\npm-cache\_logs\2020-04-08T03_23_07_544Z-debug.log
文本内容 |
|