1.4 Build Command

About the execution path problem for the build command:

First, the module build granularity of ATM is the version folder under the module

Therefore, only one version can be built under the version folder

Executing commands in the Path/to/project/family/module/version directory the ATM build will only be built: Version folder

Executing commands in the Path/to/project/family/module directory ATM build builds all the version folders under the module,

Execute an ATM if you want to build only a few of them build-p Version1,version2[,versionn]

Similarly:

Executing an ATM build in the path/to/project/family directory builds all the versions of all module (family)

If you want to build only a subset of all versions under family, you need: ATM Build-p Module1,module2[,modulen]

If you want to build part of the family under partial version, this ... Temporarily need to switch to a different module directory, using ATM Build-p Version1,version2[,versionn] slowly realize

TODO: Because ATM provides a local visual interface, this will be considered as a future upgrade option

Similarly

Executing an ATM build in the Path/to/project directory builds all of the module's versions under all family under project

Execute commands under Project to specify partial family:

ATM Build-p Family1,family2[,familyn]

PS: In addition to executing commands under version No need to confirm, in other directories are required to confirm

The following ATM deploy principle is consistent with build

1.4 Build Command