X-Git-Url: https://juplo.de/gitweb/?p=website;a=blobdiff_plain;f=dist%2Fhibernate4-maven-plugin-1.0.4%2Fskip.html;fp=dist%2Fhibernate4-maven-plugin-1.0.4%2Fskip.html;h=0000000000000000000000000000000000000000;hp=d25773931f8f7980ee0fa10eb9f535901a0a523a;hb=b293b312d6f0dd8b2dc716375fd442dd295a9942;hpb=9179a67d9952d3b63e95686dbd6cacd3c9e13cb2 diff --git a/dist/hibernate4-maven-plugin-1.0.4/skip.html b/dist/hibernate4-maven-plugin-1.0.4/skip.html deleted file mode 100644 index d2577393..00000000 --- a/dist/hibernate4-maven-plugin-1.0.4/skip.html +++ /dev/null @@ -1,194 +0,0 @@ - - - - - - - - - juplo - Hibernate 4 Maven Plugin - Skipping Execution - - - - - - - - - - - - -
- - -
-
-

Skipping Execution

- - - - -

- 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 - jetty-maven-plugin. - If the export-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 - 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, - by setting the configuration-parameter skip to false: -

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

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

- - -
-
- - -
-
- -
- - -