hibernate:hbm-code-generationhibernate:schema-update
+ This plugin provides easy integration with
+ Hibernate 2.x for your project.
+
+ For the moment the functionality is very limited.
+
| Property | Optional? | Description |
|---|---|---|
| maven.hibernate.properties | +No | +
+ The location of Hibernate configuration file
+ (Java properties file). This file is also set in the
+ runtime by Hibernate for configuring Hibernate Session,
+ so it's better to keep it separately from the project's
+ configuration files like
+ project.properties etc.
+ + For description of the properties take a look + at Hibernate User Guide + |
+
| maven.hibernate.quiet | +Yes | +
+ Controls verbosity of the plugin.
+ Default is set to yes
+ |
+
| maven.hibernate.text | +Yes | +
+ It defaults to no. If set to true, then the
+ generated SQL will be output only to the filesystem, not
+ inserted into the database.
+ |
+
| maven.hibernate.drop | +Yes | +
+ Indicates whether to drop to generate just a drop table script.
+ + It defaults to no
+ |
+
| maven.hibernate.delimiter | +Yes | +String used to separate commands in SQL output. | +
| maven.hibernate.output.dir | +Yes | +
+ The location of the directory where DDL SQL schema will
+ be generated by schema-export goal. It defaults to
+ ${maven.build.dir}/schema
+ |
+
| maven.hibernate.output.file | +Yes | +
+ The name of the file which will be created by schema-export
+ goal. It defaults to
+ ${maven.hibernate.output.dir}/${maven.final.name}-schema.sql.
+ |
+
| maven.hibernate.input.dir | +Yes | +
+ Comma-seperated list of base directories indicating where
+ mapping files are located. It defaults
+ to ${maven.build.dest}.
+ |
+
| maven.hibernate.input.includes | +Yes | +
+ Comma-separated list of patterns of Hibernate mapping files,
+ which will be included during generation process.
+ + Note: Files are relative to + ${maven.hibernate.input.dir}.
+ + By defaults all files are included: + **/*.hbm.xml.
+ |
+
| maven.hibernate.input.excludes | +Yes | +
+ Comma-separated list of patterns of Hibernate mapping files,
+ which will be excluded during generation process.
+ + Note: Files are relative to + ${maven.hibernate.input.dir}.
+ + By default no files are excluded. + |
+
| maven.hibernate.aggregate.output.file | +Yes | +When aggregate-mappings is run, this file will contain the aggregated mappings |
+
| maven.hibernate.generated.input.dir | +Yes | +Comma-seperated list of base directories indicating where mapping files are located.
+ When hbm code generation is run, the hbm files used to generate the Java files
+ should be located in these directories. It defaults to
+ ${maven.src.dir}/main.
+ |
+
| maven.hibernate.generated.input.excludes | +Yes | +
+ Comma-separated list of patterns of Hibernate mapping files,
+ which will be excluded during generation process.
+ + Note: Files are relative to + ${maven.hibernate.generated.input.dir}.
+ + By default no files are excluded. + |
+
| maven.hibernate.generated.input.includes | +Yes | +
+ Comma-separated list of patterns of Hibernate mapping files,
+ which will be included during generation process.
+ + Note: Files are relative to + ${maven.hibernate.generated.input.dir}.
+ + By defaults all files are included: + **/*.hbm.xml.
+ |
+
| maven.hibernate.generated.output.dir | +Yes | +When hbm code generation is run, the generated Java files will be placed in
+ this directory. It defaults to
+ ${maven.src.dir}/main. |
+