From: Kai Moritz Date: Sun, 11 Jan 2026 11:29:52 +0000 (+0100) Subject: Switched to `maven-hugo-skin` -- ALIGN X-Git-Url: http://juplo.de/gitweb/?a=commitdiff_plain;h=9dcc3400750b8f355748314ed000308a418ebf88;p=hibernate4-maven-plugin Switched to `maven-hugo-skin` -- ALIGN --- diff --git a/src/site/markdown/configuration.md b/src/site/markdown/configuration.md index c2c9fb83..41faa259 100644 --- a/src/site/markdown/configuration.md +++ b/src/site/markdown/configuration.md @@ -1,11 +1,7 @@ - - - - - - -

Configuration Examples

Configuration through a hibernate.properties-File

+# Configuration Examples + +## Configuration through a hibernate.properties-File +

The most simple way to configure the plugin is, to put all the hibernate-configuration in a hibernate.properties-file on your @@ -29,7 +25,8 @@ </goals> </execution> </executions> -</plugin> +</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 @@ -59,15 +56,18 @@ <configuration> <url><![CDATA[jdbc:mysql://localhost/test-db]]></url> </configuration> -</plugin> +</plugin> +

Configuration properties, that are set in the configuration-section of the plugin-configuration cannnot be overwritten elsewere (for details - see Configuration-Method-Precedence). + see Configuration-Method-Precedence). You never can overwrite them by accident when specifying a property on the commandline or in your settings.xml.

Configuration through maven-properties

+ +## Configuration through maven-properties +

Alternatively, it is possible, to configure the plugin via maven-properties. Each relevant configuration-option has a corresponding maven-property @@ -94,6 +94,7 @@ testing):

+
 <properties>
   <hibernate.connection.driver_class>org.hsqldb.jdbcDriver</hibernate.connection.driver_class>
   <hibernate.dialect>org.hibernate.dialect.HSQLDialect</hibernate.dialect>
@@ -124,7 +125,14 @@
     </configuration>
   </plugin>
 
-<plugins>

+<plugins> + +

+ This way, you can reuse the same properties to provide a + default-configurationthe, that is build into your application, and + overwrite the database-url, that is used during testing to prevent + accidential drops of your production database. +

Configuration through the plugin-configuration

A third way for configuring the plugin is the plugin-configuration. @@ -160,7 +168,8 @@ <username>sa</username> <password></password> </configuration> -</plugin> +</plugin> +

The parameter hibernateProperties (name of the hibernate-properties-file to use, defaults to hibernate.properties) can only be configured through @@ -170,7 +179,9 @@ For more explanations, see the Documentation of the export-Mojo.

Configuration-Method-Precedence

+ +## Configuration-Method-Precedence +

The configuration is gathered in a fix order:

@@ -210,6 +221,5 @@ <configuration> <password>${my-password-property}</password> </configuration> -</plugin> - - +</plugin> + diff --git a/src/site/markdown/debugging.md b/src/site/markdown/debugging.md index 9ea89247..b2321e13 100644 --- a/src/site/markdown/debugging.md +++ b/src/site/markdown/debugging.md @@ -1,10 +1,5 @@ - - - - - - -

Enable Debugging-Output

+# Enable Debugging-Output +

If you are new to hibernate4-maven-plugin, in many cases, the {Configuration-Method-Precedence} may be the source of configuration @@ -27,5 +22,3 @@ mvn -X compile hibernate4:export

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

- - diff --git a/src/site/markdown/force.md b/src/site/markdown/force.md index 0e42fd0c..b6064132 100644 --- a/src/site/markdown/force.md +++ b/src/site/markdown/force.md @@ -1,10 +1,5 @@ - - - - - - -

Force Execution

+# Force Execution +

The hibernate4-maven-plugin computes MD5-sums for all found annotated classes and stores them together with the generated schema. @@ -37,5 +32,3 @@ Or you may specify -Dhibernate.export.force=true at the command line, if you want to force hibernate4-maven-plugin only once.

- - diff --git a/src/site/markdown/index.md b/src/site/markdown/index.md index d718b811..f0502e59 100644 --- a/src/site/markdown/index.md +++ b/src/site/markdown/index.md @@ -1,11 +1,7 @@ - - - - - - -

${project.name}

${project.description}

+# ${project.name} + +## ${project.description} +

The hibernate4-maven-plugin is a plugin for generating a database-schema from your Hibernate-4-Mappings and create or update your database @@ -41,7 +37,9 @@ For more information about the inspiration to write this tiny plugin, read our blog-article about the hibernate4-maven-plugin.

Documentation

+ +## Documentation +

See Configuration Examples for Usage-Explanations @@ -55,7 +53,9 @@ the work in the background.

Releases

+ +## Releases +

current version
${project.version} (this version)
1.0.1
1.0

- - diff --git a/src/site/markdown/issue-tracking.md b/src/site/markdown/issue-tracking.md deleted file mode 100644 index 40e609d8..00000000 --- a/src/site/markdown/issue-tracking.md +++ /dev/null @@ -1,14 +0,0 @@ - - - - - - -

Issue Tracking

- There is no bug-tracking system set up for this project! -

- Please send your bug-reports, questions or feature-requests directly - to the developer. -

- - diff --git a/src/site/markdown/mail-lists.md b/src/site/markdown/mail-lists.md deleted file mode 100644 index 3dbb7330..00000000 --- a/src/site/markdown/mail-lists.md +++ /dev/null @@ -1,14 +0,0 @@ - - - - - - -

Mailing Lists

- There are no mailinglists defined for this project! -

- Please send your bug-reports, questions or feature-requests directly - to the developer. -

- - diff --git a/src/site/markdown/pitfalls.md b/src/site/markdown/pitfalls.md index a29abba0..9cfba8a1 100644 --- a/src/site/markdown/pitfalls.md +++ b/src/site/markdown/pitfalls.md @@ -1,11 +1,7 @@ - - - - - - -

Known Pitfalls (FAQ)

Annotated classes in dependencies are not found.

+# Known Pitfalls (FAQ) + +## Annotated classes in dependencies are not found. +

hibernate4-maven-plugin by default scans dependencies in the scope compile. You can configure it to scan dependencies in other @@ -14,7 +10,9 @@ annotated classes are hidden in a transitive dependency, you can simply add that dependency explicitly.

hibernate4-maven-plugin always needs a database-connection

+ +## hibernate4-maven-plugin always needs a database-connection +

The default-configuration uses the EXPORT-target of the SchemaExport-Tool. If you do not need to create a database with the evaluated schema, you can @@ -30,7 +28,9 @@ But even when no database is to be created, hibernate always needs to know the dialect. Hence, the plugin will fail if this parameter is missing!

Dependency for driver-class XYZ is missing

+ +## Dependency for driver-class XYZ is missing +

One regular problem is the scope of the jdbc-driver-dependency. It is very unlikely, that this dependency is needed at compile-time. @@ -94,7 +94,9 @@ Because otherwise, this dependency will unnecessarily bloat the runtime-dependencies of your project.

DBUnit fails after execution of hibernate4 was skipped because nothing has changed

+ +## DBUnit fails after execution of hibernate was skipped because nothing has changed +

If hibernate4-maven-plugin skips its excecution, this may lead to errors in other plugins. @@ -126,7 +128,9 @@ <skip>${hibernate.export.skipped}</skip> </configuration> </plugin> -

The database will not be recreated after a manual drop/clean

+ +## The database will not be recreated after a manual drop/clean +

If one manually drops the database or removes the hsqldb-files, it will not be recreated by the hibernate4-maven-plugin, because it cannot detect, that @@ -144,8 +148,10 @@ Otherwise the recreation must be forced:

-mvn hibernate4:export -Dhibernate.export.force=true

The hibernate4:export goal is not executed, when tests are skipped

+mvn hibernate4:create -Dhibernate.schema.force=true + +## The hibernate:create goal is not executed, when tests are skipped +

The hibernate4-maven-plugin automatically skips its execution, when maven.test.skip is set to true. If you need it to be always @@ -164,7 +170,9 @@ mvn hibernate4:export -Dhibernate.export.force=true Background-information for this design-decission can be found on the extra page To skip or not to skip: that is the question...

I do not want my dependencies to be scanned for hibernate annotations

+ +## I do not want my dependencies to be scanned for hibernate annotations +

If you do not want your dependencies to be scanned for hibernate annotations, you can pass -Dhibernate.export.scan_dependencies=none to maven @@ -180,7 +188,9 @@ mvn hibernate4:export -Dhibernate.export.force=true <scanDependencies>none</scanDependencies> </configuration> </plugin> -

No annotated classes found

+ +## No annotated classes found +

If you are working under Windows and get the error-message No annotated classes found in directory C:\projects\X Y Z\path-to-project\target\classes, @@ -193,5 +203,3 @@ mvn hibernate4:export -Dhibernate.export.force=true You should consider to upgrade to that version of the plugin.

- - diff --git a/src/site/markdown/skip.md b/src/site/markdown/skip.md index 685d4eec..989449c4 100644 --- a/src/site/markdown/skip.md +++ b/src/site/markdown/skip.md @@ -1,10 +1,5 @@ - - - - - - -

Skipping Execution

+# Skipping Execution +

In most use-cases, the hibernate4-maven-plugin is used to create a test-database automatically. In this use-cases, it is very likely, that it @@ -56,5 +51,3 @@ foo.bar to true. For example, if you specify -Dfoo.bar=true on the command-line.

- - diff --git a/src/site/site.xml b/src/site/site.xml index e84a4940..f591ede2 100644 --- a/src/site/site.xml +++ b/src/site/site.xml @@ -1,7 +1,7 @@ - + @@ -15,15 +15,7 @@ de.juplo.maven - maven-thymeleaf-skin - 1.1.2 + maven-siteliberator-skin + 1.0.0-SNAPSHOT - - - /projects - /hibernate-maven-plugin/ - "/index.html","/projects.html" - th:replace="~{/templates/layout.html :: layout(uri='' + ~{:: code[class='site_uri']/text()}, title=~{:: title}, maincontent=~{:: .maincontent}, json='MERGE:' + ~{:: pre[class='json']/text()})}" - -