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.
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.
<li><code>url</code></li>
<li><code>username</code></li>
<li><code>password</code></li>
<li><code>url</code></li>
<li><code>username</code></li>
<li><code>password</code></li>
- <driverClassName>org.hsqldb.jdbcDriver</driverClassName>
- <hibernateDialect>org.hibernate.dialect.HSQLDialect</hibernateDialect>
+ <driver>org.hsqldb.jdbcDriver</driver>
+ <dialect>org.hibernate.dialect.HSQLDialect</dialect>
<url><![CDATA[jdbc:hsqldb:target/db/fotos;shutdown=true]]></url>
<username>sa</username>
<password></password>
<url><![CDATA[jdbc:hsqldb:target/db/fotos;shutdown=true]]></url>
<username>sa</username>
<password></password>
<li>maven-properties</li>
<li>plugin-configuration</li>
</ol>
<p>
If you are in doubt about where a configuration-value comes from, run
<li>maven-properties</li>
<li>plugin-configuration</li>
</ol>
<p>
If you are in doubt about where a configuration-value comes from, run
and be aware, that maven-properties can be overwitten on the command-line,
in your <code>~/.m2/settings.xml</code> and in a profile.
</p>
and be aware, that maven-properties can be overwitten on the command-line,
in your <code>~/.m2/settings.xml</code> and in a profile.
</p>
maven-properties, you can use maven-properties in the plugin-configuration:
</p>
<pre class="prettyprint linenums lang-html">
<plugin>
<groupId>de.juplo</groupId>
maven-properties, you can use maven-properties in the plugin-configuration:
</p>
<pre class="prettyprint linenums lang-html">
<plugin>
<groupId>de.juplo</groupId>