Running Ibator With Ant

Ibator includes a simple Ant task. The task must be defined in your build.xml file, and the task has three parameters. Here is an example build.xml file:

   <project default="genfiles" basedir=".">
     <property name="generated.source.dir" value="${basedir}" />

     <target name="genfiles" description="Generate the files">
       <taskdef name="ibator"
                classname="org.apache.ibatis.ibator.ant.IbatorAntTask"
                classpath="ibator.jar" />
       <ibator overwrite="true" configfile="ibatorConfig.xml" verbose="false" >
         <propertyset>
           <propertyref name="generated.source.dir"/>
         </propertyset>
       </ibator>
     </target>
   </project>

Ibator task attributes are as follows:

Attribute	Value
configfile (required)	Specifies the name of the configuration file.
overwrite (optional)	If "true", "yes", etc., then existing Java files will be overwritten if an existing Java file if found with the same name as a generated file. If "false", "no", etc., and a Java file already exists with the same name as a generated file, then Ibator will write the newly generated Java file to the proper directory with a unique name (e.g. MyClass.java.1, MyClass.java.2, etc.). Important: Ibator will always merge and overwrite XML files.
contextids (optional)	If specified, then this is a comma delimited list of contexts to use in the current run of Ibator. Any id specified in the list must exactly match the value of the `id` attribute of an <ibatorContext> configuration element. Only ids specified in this list will be active for this run of Ibator. If this argument is not specified, then all contexts will be active.
tables (optional)	If specified, then this is a comma delimited list of tables to use in the current run of Ibator. Any table specified in the list must exactly match the fully qualified table name specified in a <table> configuration element. Only tables specified in this list will be active for this run of Ibator. If this argument is not specified, then all tables will be active. Specify table names as: `table` `schema.table` `catalog..table` etc.
verbose (optional)	If "true", "yes", etc., then Ibator will log progress messages to the ant console (if Ant is running in verbose mode). The default is "false".

Notes:

The classpath on the <taskdef> is used to tell Ant where the Ibator JAR file is. This is optional if you add Ibator to the Ant classpath in one of the other ways described in the Ant manual
The name of the task can be anything you desire, "ibator" is simply an example
The task supports an optional nested <propertyset> element which is the standard Ant property set type. This can be used to pass parameters into a configuration file. For example, the above property generated.source.dir can be accessed in the Ibator configuration file with the escape sequence ${generated.source.dir}
If a property is specified in the configuration file and is not resolved, then the escaped property string will be passed "as is" into the generated code.