X-Git-Url: https://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fxhtml%2Fskip.xhtml;h=9b570c9fb12860c23a42ba564d07f9ace3a915b8;hp=5f893b82f75853538c4a600369ed9e2e5794798b;hb=2ec0af491d992d9c26000f803bbc61fdb1299318;hpb=4940080670944a15916c68fb294e18a6bfef12d5 diff --git a/src/site/xhtml/skip.xhtml b/src/site/xhtml/skip.xhtml index 5f893b82..9b570c9f 100644 --- a/src/site/xhtml/skip.xhtml +++ b/src/site/xhtml/skip.xhtml @@ -4,6 +4,7 @@ +

Skipping Execution

In most use-cases, the hibernate-maven-plugin is used to create a test-database automatically. In this use-cases, it is very likely, that it @@ -13,7 +14,7 @@ the production-database, in order to run other tests, like starting a local webserver with the jetty-maven-plugin. - If the export-goal would be executed in such a scenario, it might erase the + If the drop-goal would be executed in such a scenario, it might erase the hole production-database, which is not very desireable.

@@ -23,8 +24,8 @@ skipped. Think of it as a build-in security-belt.

- 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, + If you do not like that, because you need the plugin to always, + even if the tests are skipped you can configure that explicitly, by setting the configuration-parameter skip to false:

@@ -37,7 +38,7 @@
   </configuration>
 </plugin>

- Or, if you want the export-goal to be executed by default and to be skipped + Or, if you want the plugin to be executed by default and to be skipped if you say so, you can bind the value of the configuration-parameter skip to a custom property. For example:

@@ -51,7 +52,7 @@ </configuration> </plugin>

- This way, the export-goal would be skipped, if you set the property + This way, the plugin would be skipped, if you set the property foo.bar to true. For example, if you specify -Dfoo.bar=true on the command-line.