From 856dd31c9b90708e841163c91261a865f9efd224 Mon Sep 17 00:00:00 2001
From: Kai Moritz
Date: Mon, 2 Jun 2014 10:12:24 +0200
Subject: [PATCH] Updated documentation
---
src/site/xhtml/configuration.xhtml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/site/xhtml/configuration.xhtml b/src/site/xhtml/configuration.xhtml
index bfaf6fec..e3ce8bcf 100644
--- a/src/site/xhtml/configuration.xhtml
+++ b/src/site/xhtml/configuration.xhtml
@@ -33,13 +33,14 @@
But be aware, that in this case the database-url, that is
build in the application is the same that is used while testing, where
the database is droped and recreated by the plugin.
+ Because of that,
- So, you should never fire up this configuration on your production
+ you should never fire up this configuration on your production
system, or your database might be erased!
- Hence, you should specify a different url for testing like in the
+ A better approach is, to specify a different url for testing like in the
following snippet:
@@ -190,7 +191,7 @@
other configuration-method.
- If you realy need to overwrite plugin-configuration-values with
+ If you need to overwrite plugin-configuration-values with
maven-properties, you can use maven-properties in the plugin-configuration:
--
2.20.1