--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ </head>
+ <body>
+ <p>
+ In most use-cases, the hibernate4-maven-plugin is used to create a
+ test-database automatically. In this use-cases, it is very likely, that it
+ will result in mistakes/errors, if the goal is executed, when the tests
+ are skipped.
+ For example, one might manually overwrite the database-url with the url of
+ the production-database, in order to run other tests, like starting a
+ local webserver with the
+ <a href="http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin">jetty-maven-plugin</a>.
+ If the export-goal would be executed in such a scenario, it might erase the
+ hole production-database, which is not very desireable.
+ </p>
+ <p>
+ Because of this, the configuration-parameter <code>skip</code> defaults to the value
+ of the proptery <code>maven.test.skip</code>. This way, the execution of the
+ hibernate4-maven-plugin is skipped automatically, when the tests are
+ skipped. Think of it as a build-in security-belt.
+ </p>
+ <p>
+ If you do not like that, because you need the plugin to always execute the
+ export-goal, even if the tests are skipped you can configure that explicitly,
+ by setting the configuration-parameter <code>skip</code> to false:
+ </p>
+ <pre class="prettyprint linenums lang-html">
+<plugin>
+ <groupId>de.juplo</groupId>
+ <artifactId>hibernate4-maven-plugin</artifactId>
+ ...
+ <configuration>
+ <skip>false</skip>
+ </configuration>
+</plugin></pre>
+ <p>
+ Or, if you want the export-goal to be executed by default and to be skipped
+ if you say so, you can bind the value of the configuration-parameter
+ <code>skip</code> to a custom property. For example:
+ </p>
+ <pre class="prettyprint linenums lang-html">
+<plugin>
+ <groupId>de.juplo</groupId>
+ <artifactId>hibernate4-maven-plugin</artifactId>
+ ...
+ <configuration>
+ <skip>${foo.bar}</skip>
+ </configuration>
+</plugin></pre>
+ <p>
+ This way, the export-goal would be skipped, if you set the property
+ <code>foo.bar</code> to <code>true</code>. For example, if you specify <code>-Dfoo.bar=true</code>
+ on the command-line.
+ </p>
+ </body>
+</html>