<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>
<body>
+ <header><h1>Force Execution</h1></header>
<p>
The hibernate-maven-plugin computes MD5-sums for all found annotated
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.
</p>
<p>
The plugin signals, that the execution was skipped by setting the maven
- property <code>$\{hibernate.export.skipped\}</code> to <code>true</code>.
+ property <code>${hibernate.schema.skipped}</code> to <code>true</code>.
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>
- If you need the hibernate-maven-plugin to <never skip execution automatically>,
+ If you need the hibernate-maven-plugin to <em>never skip execution automatically</em>,
you can force it to do so, if you set the parameter <code>force</code> to
<code>true</code>:
</p>
</configuration>
</plugin></pre>
<p>
- Or you may specify <code>-Dhibernate.export.force=true</code> at the command line,
+ Or you may specify <code>-Dhibernate.schema.force=true</code> at the command line,
if you want to force hibernate-maven-plugin only once.
</p>
</body>