如何在extjs4.1中修复构建错误com.sencha.exceptions.ExProcess

Question

我在构建extjs4.1项目时遇到以下异常。 谁能告诉我如何避免它？ 我正在使用sencha命令版本3.0。 使用命令

sencha app build


[ERR]           D:\TestProduction\.sencha\app\build-impl.xml:213: com.sencha.exc
eptions.ExProcess: phantomjs process exited with code 100 :

谢谢

Answer 1

我遇到了运行sencha app build的同样问题：

 [...] [INF] loading page .../static/sass/example/theme.html failed to render widgets within 30 sec. [ERR] [ERR] BUILD FAILED [ERR] com.sencha.exceptions.ExProcess: phantomjs process exited with code 1 [ERR] [ERR] Total time: 49 seconds [ERR] The following error occurred while executing this line: .../static/.sencha/app/build-impl.xml:469: com.sencha.exceptions.ExProcess: phantomjs process exited with code 1 

我的项目目录似乎缺少sass文件夹。

所以我创建了一个新的应用程序并从那里复制了sass文件夹：

 $ cd /tmp $ sencha -s ~/develop/js/Sencha/ext-4.2.1.883 generate app MyApp myapp $ tree myapp/sass myapp/sass ├── config.rb ├── etc ├── example │   ├── bootstrap.css │   ├── custom.js │   ├── render.js │   └── theme.html ├── src └── var $ cp -r myapp/sass <dest> 

我还尝试将sass文件夹直接从我的应用程序中的ext文件夹中复制出来：

$ cp -r ext / packages / ext-theme-classic / sass。

但似乎没有设置一些路径。 所以我不得不手动编辑文件theme.html ：

 $ vim sass/example/theme.html [...] <!-- These links need to match the ext sdk from the current project --> <link rel="stylesheet" type="text/css" href="example.css" /> <script type="text/javascript" src="../../ext/ext-dev.js"></script> <script type="text/javascript" src="bootstrap.js"></script> 

在此之后，我又能够做一个sencha app build ：

$ sencha app build
[...]

[INF] loading page .../static/sass/example/theme.html
Capturing screenshot
Saving slicer widget manifest
Capture complete

[INF] Capture complete
[INF]      [echo] Slicing theme images to .../static/build/CreateProduct/production/resources
[INF] Including theme package ext-theme-classic for app.theme=ext-theme-classic build
[INF] Slicing images...
[INF] Slicing complete - generated 0 images
[INF]
[INF] -after-slice:
[INF]
[INF] -build:
[INF]
[INF] -after-build:
[INF]
[INF] build:
[INF]
[INF] app-build:

Answer 2

我有同样的问题，它似乎与客户端路径有关，在路径名中包含“＃”，即c：\\ projects \\ c＃\\ project \\ client

在不同的目录中生成应用程序解决了这个问题