| 1695 |
bivey |
1 |
<project name="ant-apmcfg">
|
|
|
2 |
<taskdef name="apmcfg" classname="com.erggroup.mass.ant.tasks.Apmcfg" classpath="${using.ant-apmcfg.basedir}/jar/ant-apmcfg.jar" />
|
|
|
3 |
|
|
|
4 |
<!--
|
|
|
5 |
APMCFG payload can be generated using the following syntax in an ANT script:
|
|
|
6 |
|
|
|
7 |
<apmcfg version="1" // The overall software build version (req)
|
|
|
8 |
dir="build"> // Directory to write the @APMCFG.mug file (default: working path)
|
|
|
9 |
|
|
|
10 |
<device type="ATDA" // The device type name, max 9 chars (req)
|
|
|
11 |
tier="3" // Where the device type is in the network hierarchy (default: 3)
|
|
|
12 |
version="1"> // Software release version (default: apmcfg version)
|
|
|
13 |
|
|
|
14 |
<module file="avmupg.zip" // The file associated with this module (req)
|
|
|
15 |
tag="AVMAPP" // Software module name, max 8 chars (default: derived from file name)
|
|
|
16 |
version=1" // Software module version (default: device type version)
|
|
|
17 |
type="0" // A bitmap controlling the software module loading process (default: 0)
|
|
|
18 |
special="0"/> // Indicates if the software module has special memory requirements (default: 0)
|
|
|
19 |
...
|
|
|
20 |
</device>
|
|
|
21 |
...
|
|
|
22 |
|
|
|
23 |
</apmcfg>
|
|
|
24 |
-->
|
|
|
25 |
</project>
|