X-Git-Url: https://juplo.de/gitweb/?p=website;a=blobdiff_plain;f=dist%2Fhibernate4-maven-plugin-1.0.5%2Fdebugging.html;fp=dist%2Fhibernate4-maven-plugin-1.0.5%2Fdebugging.html;h=01eedf8675dbae218d48f2a6f4768368a24aa3b8;hp=0000000000000000000000000000000000000000;hb=a53595184bd6e57bdc45292cc92c393c4e2dfe6e;hpb=c48c9ee0e9faa89a4c0a5323b367b9f5a6abe602 diff --git a/dist/hibernate4-maven-plugin-1.0.5/debugging.html b/dist/hibernate4-maven-plugin-1.0.5/debugging.html new file mode 100644 index 00000000..01eedf86 --- /dev/null +++ b/dist/hibernate4-maven-plugin-1.0.5/debugging.html @@ -0,0 +1,162 @@ + + + + + + + + + juplo - Hibernate 4 Maven Plugin - Enable Debug-Output + + + + + + + + + + + + +
+ + +
+
+

Enable Debug-Output

+ + + + +

+ If you are new to hibernate4-maven-plugin, in many cases, the + {Configuration-Method-Precedence} may be the source of configuration + errors. + To solve this problem, you should run maven with the debugging output + enabled. + For example, by executing: +

+ +
+
+mvn -X compile hibernate4:export
+ +

+ (The compile might be necessary, because hibernate4-maven-plugin + has to scan the compiled classes for annotations!) +

+ +

+ Unlike the majority of the maven-plugins, hibernate4-maven-plugin was + designed to give a good many hints, when debugging is enabled. + Because, if you do not know, what went wrong, you can't fix it! +

+ +

+ But be warned: hibernate4-maven-plugin tends to be very chatty ;) +

+ + +
+
+ + +
+
+ +
+ + +