X-Git-Url: https://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fxhtml%2Fskip.xhtml;h=e25ed0ed39cd22cef1ffc6afdef76ac959560716;hp=51a20af746243d94058ec442b2a68c9dc2249ce7;hb=0611db682bc69b80d8567bf9316668a1b6161725;hpb=64900890db2575b7a28790c5e4d5f45083ee94b3 diff --git a/src/site/xhtml/skip.xhtml b/src/site/xhtml/skip.xhtml index 51a20af7..e25ed0ed 100644 --- a/src/site/xhtml/skip.xhtml +++ b/src/site/xhtml/skip.xhtml @@ -5,7 +5,7 @@

- In most use-cases, the hibernate4-maven-plugin is used to create a + 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 will result in mistakes/errors, if the goal is executed, when the tests are skipped. @@ -13,45 +13,45 @@ 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.

Because of this, the configuration-parameter skip defaults to the value of the proptery maven.test.skip. This way, the execution of the - hibernate4-maven-plugin is skipped automatically, when the tests are + hibernate-maven-plugin is skipped automatically, when the tests are 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:

 <plugin>
   <groupId>de.juplo</groupId>
-  <artifactId>hibernate4-maven-plugin</artifactId>
+  <artifactId>hibernate-maven-plugin</artifactId>
   ...
   <configuration>
     <skip>false</skip>
   </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:

 <plugin>
   <groupId>de.juplo</groupId>
-  <artifactId>hibernate4-maven-plugin</artifactId>
+  <artifactId>hibernate-maven-plugin</artifactId>
   ...
   <configuration>
     <skip>${foo.bar}</skip>
   </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.