Task Name | Description |
---|---|
mulePackage | Creates a Mule application archive |
muleDeploy | Deploys a Mule application |
-lib mule-anttasks.jar
to your Ant command line, to put the classes that implement the tasks in Ant's classpath.<taskdef resource="org/mule/mulePackagingTasks.properties"/>
to your Ant build file,
to import the task definitions.Create a Mule application archive.
Attribute | Description | Required |
applicationFile | the application file to be created | Yes |
Element | Description |
config | A FileSet specifying configuration files to be placed at the top level of the application. |
lib | A FileSet specifying jar files to be placed in the application's lib folder. |
classes | A FileSet specifying class and resource files to be placed in the application's classes folder. |
<mulePackage applicationFile="${app.file}"> <config dir="src/app"/> <lib dir="target/lib"/> </mulePackage>
packages the application ${app.file}
using the
configuration files in the config
directory and the jars in the
lib
directory. In this example, there were no classes or resources outside the jars.
<mulePackage applicationFile="${app.file}"> <config dir="src/app"/> <classes dir="target/classes"/> <lib dir="target/lib"/> </mulePackage>
packages the application ${app.file}
using the
configuration files in the config
directory, the
classes and resources in the classes
directory, and the jars in the
lib
directory.
Deploys a Mule application archive.
Attribute | Description | Required |
applicationFile | the application file to deploy | Yes |
muleHome | the base directory for the Mule installation. | No |
<muleDeploy applicationFile="${app.file}"/>
deploys the application ${app.file}
to the mule installation at
${dir.mule.home}
, which can be set either in the Ant build file or on the Ant command line.
<muleDeploy applicationFile="${app.file}" muleHome="/usr/opt/mule"/>
deploys the application ${app.file}
to the mule installation at
/usr/opt/mule
.