classes and stores them together with the generated schema.
If no classes were changed or added and the dialect wasn't changed too, it
classes and stores them together with the generated schema.
If no classes were changed or added and the dialect wasn't changed too, it
- automatically skips the configured schema-export, to speed up the development
- cycle.
+ automatically skips the configured SQL-generation — and more
+ important in this respect — the execution of the generated SQL,
+ to speed up the development cycle.
This may be helpful, because other plugins like
<a href="http://mojo.codehaus.org/dbunit-maven-plugin/">dbunit-plugin</a>
<a href="./pitfalls.html#fails">may fail</a>, when the execution is skipped.
</p>
<p>
This may be helpful, because other plugins like
<a href="http://mojo.codehaus.org/dbunit-maven-plugin/">dbunit-plugin</a>
<a href="./pitfalls.html#fails">may fail</a>, when the execution is skipped.
</p>
<p>
you can force it to do so, if you set the parameter <code>force</code> to
<code>true</code>:
</p>
<pre class="prettyprint linenums lang-html">
<plugin>
<groupId>de.juplo</groupId>
you can force it to do so, if you set the parameter <code>force</code> to
<code>true</code>:
</p>
<pre class="prettyprint linenums lang-html">
<plugin>
<groupId>de.juplo</groupId>
- Or you may specify <code>-Dhibernate.export.force=true</code> at the command line,
- if you want to force hibernate4-maven-plugin only once.
+ Or you may specify <code>-Dhibernate.schema.force=true</code> at the command line,
+ if you want to force hibernate-maven-plugin only once.