Usage

The execution of this plugin's mojo can be bound to a phase of build lifecycle. Use the dependencies in plugin to specify the artifact that has your JDBC driver.

<project>
  [...]
  <build>
    [...]
    <plugins>
      [...]
      <plugin>
        <groupId>org.dbunit</groupId>
        <artifactId>dbunit-maven-plugin</artifactId>
        <version>1.2.0</version>
        
        <!--jar file that has the jdbc driver -->
        <dependencies>
          <dependency>
            <groupId></groupId>
            <artifactId></artifactId>
            <version></version>
          </dependency>
        </dependencies>
        
        <!-- common configurations -->
        <configuration>
          <driver></driver>
          <url></url>
          <username></username>
          <password><password>
          [....]
        </configuration>
        
        </executions>
          <execution>
            <phase></phase>
            <goals>
              <goal></goal>
            </goals>
            <!-- specific configurations -->
            <configuration>
              [...]
            </configuration>
          </execution>
          <execution>
            <phase></phase>
            <goals>
              <goal></goal>
            </goals>
            <!-- specific configurations -->
            <configuration>
              [...]
            </configuration>
          </execution>
          [...]
        </executions>
        
        [...]
      </plugin>
      [...]
    </plugins>
    [...]
  </build>
  [...]
</project>

The configuration element can contain all properties and features that are known to the DatabaseConfig class (see http://dbunit.sourceforge.net/properties.html ). It allows to specify the short name of the properties in the same way it works for the ant task: http://dbunit.sourceforge.net//anttask.html Note that there are still the old and deprecated configuration elements (not nested in the dbconfig element but specified explicitly beneath the configuration). If you specify your properties in both ways then the dbconfig value will always have precedence over the old ones.

[...]
<configuration>
  <dbconfig>
      <property>
        <name>datatypeFactory</name>
        <value>org.dbunit.ext.hsqldb.HsqldbDataTypeFactory</value>
      </property>
      <property>
        <name>tableType</name>
        <value>TABLE,SYNONYM</value>
      </property>
      <property>
        <name>batchedStatements</name>
        <value>true</value>
      </property>
      <property>
        <name>caseSensitiveTableNames</name>
        <value>true</value>
      </property>
  </dbconfig>
</configuration>
[...]