-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>Configuration Examples</h1></header>
- <h2>Configuration Through A Configuration-File</h2>
+# Configuration Examples
+
+## Configuration Through A Configuration-File
+
<p>
The most simple way to configure the plugin is, to put all the
hibernate-configuration in a <strong>hibernate.properties</strong>- or
</goals>
</execution>
</executions>
-</plugin></pre>
+</plugin>
+</pre>
<p>
This would create the configured database.
If you want it to be droped beforehand, you have to add the goal
</goals>
</execution>
</executions>
-</plugin></pre>
+</plugin>
+</pre>
<p>
A correspondin goal for the command <code>update</code> is missing in this
version, but we are planning to implement it in near feature.
hibernate.connection.url=jdbc:h2:file:./target/db
hibernate.connection.driver_class=org.h2.Driver
hibernate.connection.username=sa
-hibernate.connection.password=</pre>
+hibernate.connection.password=
+</pre>
<p>
But be aware, that using this configuration-approach the database-url,
that is build in the application is the same that is used while testing,
<configuration>
<url><![CDATA[jdbc:mysql://localhost/test-db]]></url>
</configuration>
-</plugin></pre>
+</plugin>
+</pre>
<p>
Configuration properties, that are set in the <code>configuration</code>-section
of the plugin-configuration cannnot be overwritten elsewere (for details
- see <a href="#precedence">Configuration-Method-Precedence</a>).
+ see <a href="#Configuration_Method_Precedence">Configuration-Method-Precedence</a>).
You never can overwrite them by accident when specifying a property on
the commandline or in your <code>settings.xml</code>.
</p>
- <h2>Configuration through maven-properties</h2>
+
+## Configuration through maven-properties
+
<p>
Alternatively, it is possible, to configure the plugin via maven-properties.
Each relevant configuration-option has a corresponding maven-property
testing):
</p>
<pre class="prettyprint linenums lang-html">
+
<properties>
<hibernate.connection.driver_class>org.hsqldb.jdbcDriver</hibernate.connection.driver_class>
<hibernate.dialect>org.hibernate.dialect.HSQLDialect</hibernate.dialect>
</configuration>
</plugin>
-<plugins></pre>
+<plugins>
+
+ </pre>
<p>
This way, you can reuse the same properties to provide a
default-configurationthe, that is build into your application, and
<username>sa</username>
<password></password>
</configuration>
-</plugin></pre>
+</plugin>
+</pre>
<p>
The parameter <strong>hibernateProperties</strong> (name of the hibernate-properties-file
to use, defaults to <strong>hibernate.properties</strong>) can only be configured through
For more explanations, see the
<a href="./create-mojo.html">Documentation of the goal create</a>.
</p>
- <h2 id="precedence">Configuration-Method-Precedence</h2>
+
+## Configuration-Method-Precedence
+
<p>
The configuration is gathered in a fix order:
</p>
<configuration>
<password>${my-password-property}</password>
</configuration>
-</plugin></pre>
- </body>
-</html>
+</plugin>
+</pre>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>Enable Debugging-Output</h1></header>
+# Enable Debugging-Output
+
<p>
If you are new to <code>hibernate-maven-plugin</code>, in many cases, the
<a href="./configuration.html#precedence">Configuration-Method-Precedence</a>
<p>
<strong>But be warned:</strong> <code>hibernate-maven-plugin</code> tends to be very chatty ;)
</p>
- </body>
-</html>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>Force Execution</h1></header>
+# Force Execution
+
<p>
The hibernate-maven-plugin computes MD5-sums for all found annotated
classes and stores them together with the generated schema.
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>
-</html>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>${project.name}</h1></header>
- <h2>${project.description}</h2>
+# ${project.name}
+
+## ${project.description}
+
<p>
The <strong>hibernate-maven-plugin</strong> is a plugin for generating a database-schema
from your Hibernate-Mappings and create or update your database
For more information about the inspiration to write this tiny plugin,
<a href="/hibernate-maven-plugin-a-simple-plugin-for-generating-a-database-schema-from-hibernate-4-mapping-annotations/">read our blog-article about the hibernate-maven-plugin</a>.
</p>
- <h2>Documentation</h2>
+
+## Documentation
+
<ul>
<li>
See <a href="./configuration.html">Configuration Examples</a> for Usage-Explanations
from the Hibernate-Tooling, that does the work in the background.
</li>
</ul>
- <h2>Releases</h2>
+
+## Releases
+
<ul>
<li><a href="${project.url}">current version</a></li>
<li>${project.version} (this version)</li>
<li><a href="/projects/hibernate-maven-plugin/1.0.1/index.html">1.0.1</a></li>
<li><a href="/projects/hibernate-maven-plugin/1.0/index.html">1.0</a></li>
</ul>
- </body>
-</html>
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>Issue Tracking</h1></header>
- <strong>There is no bug-tracking system set up for this project!</strong>
- <p>
- Please send your bug-reports, questions or feature-requests directly
- to the developer.
- </p>
- </body>
-</html>
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>Mailing Lists</h1></header>
- <strong>There are no mailinglists defined for this project!</strong>
- <p>
- Please send your bug-reports, questions or feature-requests directly
- to the developer.
- </p>
- </body>
-</html>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>Known Pitfalls (FAQ)</h1></header>
- <h2>Annotated classes in dependencies are not found.</h2>
+# Known Pitfalls (FAQ)
+
+## Annotated classes in dependencies are not found.
+
<p>
hibernate-maven-plugin by default scans dependencies in the scope
<code>compile</code>. You can configure it to scan dependencies in other
annotated classes are hidden in a transitive dependency, you can simply
add that dependency explicitly.
</p>
- <h2>hibernate-maven-plugin always needs a database-connection</h2>
+
+## hibernate-maven-plugin always needs a database-connection
+
<p>
The default-configuration executes the created SQL.
Therefore, it needs a valid database-connection and fails, if none is
the dialect. Hence, the plugin will still fail, if this parameter is also
missing!
</p>
- <h2>Dependency for driver-class XYZ is missing</h2>
+
+## Dependency for driver-class XYZ is missing
+
<p>
One regular problem is the scope of the jdbc-driver-dependency.
It is very unlikely, that this dependency is needed at compile-time.
Because otherwise, this dependency will unnecessarily bloat the
runtime-dependencies of your project.
</p>
- <h2 id="fails">DBUnit fails after execution of hibernate was skipped because nothing has changed</h2>
+
+"##DBUnit fails after execution of hibernate was skipped because nothing has changed
+
<p>
If hibernate-maven-plugin skips its excecution, this may lead to errors in
other plugins.
<skip>${hibernate.schema.skipped}</skip>
</configuration>
</plugin></pre>
- <h2>The database will not be recreated after a manual drop/clean</h2>
+
+## The database will not be recreated after a manual drop/clean
+
<p>
If one manually drops the database or removes the hsqldb-files, it will not
be recreated by the hibernate-maven-plugin, because it cannot detect, that
</p>
<pre class="prettyprint">
mvn hibernate:create -Dhibernate.schema.force=true</pre>
- <h2>The hibernate:create goal is not executed, when tests are skipped</h2>
+
+## The hibernate:create goal is not executed, when tests are skipped
+
<p>
The hibernate-maven-plugin automatically skips its execution, when
<code>maven.test.skip</code> is set to <code>true</code>. If you need it to be always
Background-information for this design-decission can be found on the extra
page <a href="./skip.html">To skip or not to skip: that is the question</a>...
</p>
- <h2>I do not want my dependencies to be scanned for hibernate annotations</h2>
+
+## I do not want my dependencies to be scanned for hibernate annotations
+
<p>
If you do not want your dependencies to be scanned for hibernate annotations,
you can pass <code>-Dhibernate.schema.scan.dependencies=none</code> to maven
<scanDependencies>none</scanDependencies>
</configuration>
</plugin></pre>
- <h2>No annotated classes found</h2>
+
+## No annotated classes found
+
<p>
If you are working under Windows and get the error-message
<code>No annotated classes found in directory C:\projects\X Y Z\path-to-project\target\classes</code>,
You should consider to upgrade to the latest version of the plugin.
</strong>
</p>
- <h2>If two goals are specified, the second one is always skipped</h2>
+
+## If two goals are specified, the second one is always skipped
+
<p>
If you specify two goals, for example <code>drop</code> and
<code>create</code>, each goal has to be specified in its own
<outputFile>db-schema/create-schema.ddl</outputFile>
</configuration>
</execution>
-</executions></pre>
- </body>
-</html>
+</executions>
+</pre>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- </head>
- <body>
- <header><h1>Skipping Execution</h1></header>
+# Skipping Execution
+
<p>
In most use-cases, the hibernate-maven-plugin is used to create a
test-database automatically. In this use-cases, it is very likely, that it
<code>foo.bar</code> to <code>true</code>. For example, if you specify <code>-Dfoo.bar=true</code>
on the command-line.
</p>
- </body>
-</html>
<project>
<body>
<menu>
- <item name="Overview" href="index.html?about"/>
+ <item name="Overview" href="index.html"/>
<item name="Configuration Examples" href="configuration.html"/>
<item name="Goal — hibernate:create" href="create-mojo.html"/>
<item name="Goal — hibernate:update" href="update-mojo.html"/>
</body>
<skin>
<groupId>de.juplo.maven</groupId>
- <artifactId>maven-thymeleaf-skin</artifactId>
- <version>1.1.2</version>
+ <artifactId>maven-siteliberator-skin</artifactId>
+ <version>1.0.0-SNAPSHOT</version>
</skin>
- <custom>
- <thymeproxy>
- <prefix>/projects</prefix>
- <path>/hibernate-maven-plugin/</path>
- <crumbs>"/index.html","/projects.html"</crumbs>
- <command>th:replace="~{/templates/layout.html :: layout(uri='' + ~{:: code[class='site_uri']/text()}, title=~{:: title}, maincontent=~{:: .maincontent}, json='MERGE:' + ~{:: pre[class='json']/text()})}"</command>
- </thymeproxy>
- </custom>
</project>
projects / hibernate-maven-plugin / commitdiff