X-Git-Url: https://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fapt%2Findex.apt;h=3698529bac02dd8d963047052caacd81655a677c;hp=3b237a2cb5bd1457f8dadcffa2b0481a353bb7b9;hb=17b00da14edf0d80c738b82dae9a4b3a1ba21ac7;hpb=d8f4466a2342587009406aae4f2a7023bc11f5ea diff --git a/src/site/apt/index.apt b/src/site/apt/index.apt index 3b237a2c..3698529b 100644 --- a/src/site/apt/index.apt +++ b/src/site/apt/index.apt @@ -1,26 +1,21 @@ -A simple plugin for generating a database-schema from Hibernate 4 mapping-annotations. +A simple Plugin for generating a Database-Schema from Hibernate 4 Mapping-Annotations. - Hibernate comes with the buildin functionality, to automatically create or - update the database schema. - This functionality is configured in the session-configuraton via the - parameter - (see {{{http://docs.jboss.org/hibernate/orm/4.1/manual/en-US/html_single/#configuration-optional} Hibernate Reference Documentation - Chapter 3.4. Optional configuration properties}}). - But doing so - {{{http://stackoverflow.com/questions/221379/hibernate-hbm2ddl-auto-update-in-production} is not very wise}}, because you can easily corrupt or erase your - production database, if this configuration parameter slips through to your - production environment. - Alternatively, you can - {{{http://stackoverflow.com/questions/835961/how-to-creata-database-schema-using-hibernate} run the tools SchemaExport or SchemaUpdate by hand}}. - But that is not very comfortable and being used to maven you will quickly - long for a plugin, that does that job automatically for you, when you fire - up your test cases. + <> is a plugin for generating a database-schema + from your Hibernate-4-Mappings and create or update your database + accordingly. - In the good old times, there was the - {{{http://mojo.codehaus.org/maven-hibernate3/hibernate3-maven-plugin/} Maven Hibernate3 Plugin}}, that does this for you. - But unfortunatly, this plugin is not compatible with Hibernate 4.x. + The plugin was designed to be easy and safe to use, because it must not + never, never happen, that you blow away your production database when + firering a maven-build of your webapp on your production-machine! + For more information about the insiration to write this tiny plugin, + {{{/hibernate4-maven-plugin-a-simple-plugin-for-generating-a-database-schema-from-hibernate-4-mapping-annotations/} read our blog-article about the hibernate4-maven-plugin}}. - Since there does not seem to be any successor for the Maven Hibernate3 Plugin - and {{{http://www.google.de/search?q=hibernate4+maven+plugin} googeling}} - does not help, I decided to write up this simple plugin (inspired by these - two articles I found: {{{http://www.tikalk.com/alm/blog/schema-export-hibernate-4-and-maven} Schema Export with Hibernate 4 and Maven}} and - {{{http://doingenterprise.blogspot.de/2012/05/schema-generation-with-hibernate-4-jpa.html} Schema generation with Hibernate 4, JPA and Maven}}). +Documentation and Examples + + * See {{{./examples.html} Examples}} for Usage-Eplanations and simple + examples of how to use this plugin. + + * See {{{./plugin-info.html} Plugin Documentation}} for the full + autogenerated documentation. These are mostly configuration-options + of the Hibernate-Tools <<>> and <<>>, that do + the work in the background.