Sencha Cmd破碎：为什么'app build'忽略任何命令行参数？ [英] Sencha Cmd broken: Why does 'app build' ignore any command line parameters?

问题描述

我已经将Sencha cmd升级到v4，我曾经能够构建到特定的归档路径和目标路径。这是至关重要的，因为构建服务器删除每个构建的源代码文件夹和归档路径。我在IIS服务器上输出的路径远离构建服务器，所以它们永远不会丢失。

但是，我的构建过程现在失败，因为路径参数提供如果我输入：

  Sencha帮助应用程序构建
  

我得到以下帮助：

 语法
 
 sencha app build [options] [environment] \ 
 [destination] \ 
 [存档] 
  

但提供这些参数对输出的位置没有影响。

任何人都可以指出文档，显示是否已更改，以及如何纠正。我的网站上找不到任何东西，显示如何构建生产，并将其输出到单独的路径。我也想知道为什么Sencha工具变化如此之多。这对任何现有的构建系统造成严重破坏，因为事情突然停止工作。

见下文：

 C：\Development\Projects\IEApp> sencha app build --archive C：\temp\build\IEApp\bui 
 ldarchive --destination C：\ temp\build\IEApp\Destination  - 环境生产
  

一切都可以，但是 C：\temp\build 文件夹为空。

解决方案

我无法告诉你doc是，但要让CMD构建到不同的目录，这就是我所做的：

修改文件：.sencha\app\production.properties as如下：

 ＃===================== ================================================== ==== 
＃此文件为
＃production.defaults.properties中定义的默认变量提供一个覆盖点。这些属性仅在为生产环境构建
＃时导入。 
＃
＃此文件中定义的属性优先于build.properties，但
＃仅为生产构建加载。 
＃========================================= ============================== 
 build.dir = $ {app.dir} /../ ../ExtJSApps/dashboard 
  

I've upgraded Sencha cmd to v4 and I used to be able to build to a specific archive path and destination path. This was crucial as the build server removes the source code folder and archive path for each build. I had the paths output on the IIS server away from the build server, so that they are never lost.

However, my build process is failing now as the path parameters supplied to the sencha cmd don't do anything.

If I type:

Sencha help app build

I get the following help:

Syntax

sencha app build [options] [environment] \
                           [destination] \
                           [archive]

But supplying these parameters has no effect to the location of the output.

Can anyone point me to the documentation which shows if this has changed and how I rectify it. I can't find anything on the their site which shows how to build for production and have it output to separate paths. Also I'd like to know why the Sencha Tools change so much. This wreaks havoc on any existing build systems because things suddenly stop working.

See below:

C:\Development\Projects\IEApp>sencha app build --archive C:\temp\build\IEApp\bui
ldarchive --destination C:\temp\build\IEApp\Destination --environment production

Everything builds ok, but the C:\temp\build folder is empty.

解决方案

I can not tell you where the doc is, but to get CMD to build to a different directory, this is what I do:

modify the file: .sencha\app\production.properties as follows:

# =============================================================================
# This file provides an override point for default variables defined in 
# production.defaults.properties. These properties are only imported when building
# for the "production" environment.
#
# Properties defined in this file take priority over build.properties but are
# only loaded for "production" builds.
# =============================================================================
build.dir=${app.dir}/../../ExtJSApps/dashboard

这篇关于Sencha Cmd破碎：为什么'app build'忽略任何命令行参数？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！