A Lure Ant task jar file is available as part of the main Lure distribution. It is located within the “ant” subfolder of the main Lure installation folder, together with an example
build.xml file. Copy these two files to any appropriate directory; then within the build.xml file update the “dir” property of the taskdef to point to the folder where the Ant task jar is located.
The Lure Ant task requires Ant 1.7 and also a running version of Lure command line to be available.
The Lure Ant task supports the following parameters as XML attributes:
|command||The Lure command to execute. Currently only deploy and patch-test and get-history are supported.||Yes|
|dryrun||If true then Lure executes the deploy command in dry-run mode. This option is only applicable to the deploy command. Defaults to false.||No|
|failOnDifference||If true then if after deploying the source code Lure detects a remaining difference between the DDL in the database and the source code on the filesystem, then the Ant task will fail with an error. Defaults to true.||No|
|connectFile||A string specifying the location of the <env>.lure-connect file.||No|
|file||A string specifying a single file or folder argument to Lure.||No|
In addition the Lure Ant task supports any number of nested path elements (i.e. the Ant based path element).
For example the following code:
<lure command="deploy" dryrun="true" failOnDifference="false" > <path> <pathelement location="C:\TEST1\nav"/> <fileset dir="C:\TEST1\data\indexes"> <include name="*.*"/> </fileset> </path> </lure>
passes the directory
C:\TEST1\nav and all files in the directory
C:\TEST1\data\indexes to Lure as arguments. Lure then executes the
deploy command in dry-run mode but does not fail if source code differences are detected.