X-Git-Url: https://juplo.de/gitweb/?a=blobdiff_plain;f=src%2Fsite%2Fxhtml%2Fskip.xhtml;h=5f893b82f75853538c4a600369ed9e2e5794798b;hb=9d6e06c972ddda45bf0cd2e6a5e11d8fa319c290;hp=51a20af746243d94058ec442b2a68c9dc2249ce7;hpb=64900890db2575b7a28790c5e4d5f45083ee94b3;p=hibernate-maven-plugin diff --git a/src/site/xhtml/skip.xhtml b/src/site/xhtml/skip.xhtml index 51a20af7..5f893b82 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. @@ -19,7 +19,7 @@
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.
@@ -30,7 +30,7 @@
<plugin> <groupId>de.juplo</groupId> - <artifactId>hibernate4-maven-plugin</artifactId> + <artifactId>hibernate-maven-plugin</artifactId> ... <configuration> <skip>false</skip> @@ -44,7 +44,7 @@<plugin> <groupId>de.juplo</groupId> - <artifactId>hibernate4-maven-plugin</artifactId> + <artifactId>hibernate-maven-plugin</artifactId> ... <configuration> <skip>${foo.bar}</skip>