Hi,
can any one tell me how to force maven to precede mapping .hbm.xml files in
the automatically generated hibernate.cfg.xml file with package path?
My general idea is, I'd like to use hibernate-tools via maven to generate
the persistence layer for my application. So, I need
the hibernate.cfg.xml, then all my_table_names.hbm.xml and at
the end
the POJO's generated. Yet,
the hbm2java goal won't work as I put *.hbm.xml files into
the src/main/resources/package/path/ folder but hbm2cfgxml specifies
the mapping files only by table
name, i.e.:
<mapping resource="MyTableName.hbm.xml" />
So
the big question is: how can I configure hbm2cfgxml so that hibernate.cfg.xml looks like below:
<mapping resource="package/path/MyTableName.hbm.xml" />
My pom.xml looks like this at
the moment:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>hibernate3-maven-plugin</artifactId>
<version>2.2</version>
<executions>
<execution>
<id>hbm2cfgxml</id>
<phase>generate-sources</phase>
<goals>
<goal>hbm2cfgxml</goal>
</goals>
<inherited>false</inherited>
<configuration>
<components>
<component>
<name>hbm2cfgxml</name>
<implemetation>jdbcconfiguration</implementation>
<outputDirectory>src/main/resources/</outputDirectory>
</component>
</components>
<componentProperties>
<packagename>package.path</packageName>
<configurationFile>src/main/resources/hibernate.cfg.xml</configurationFile>
</componentProperties>
</configuration>
</execution>
</executions>
</plugin>
And then
the second question: is there a way to tell maven to copy resources to
the target folder before executing hbm2java? At
the moment I'm using
mvn clean resources:resources generate-sources
for that, but there must be a better way.
Thanks for any help.
Update:
@Pascal: Thank you for your help.
The path to mappings works fine now, I don't know what was wrong before, though. Maybe there is some issue with writing to hibernate.cfg.xml while reading database config from it (though
the file gets updated).
I've deleted
the file hibernate.cfg.xml, replaced it with database.properties and run
the goals hbm2cfgxml and hbm2hbmxml. I also don't use
the outputDirectory nor configurationfile in those goals anymore.
As a result
the files hibernate.cfg.xml and all *.hbm.xml are being generated into my target/hibernate3/generated-mappings/ folder, which is
the default value. Then I updated
the hbm2java goal with
the following:
<componentProperties>
<packagename>package.name</packagename>
<configurationfile>target/hibernate3/generated-mappings/hibernate.cfg.xml</configurationfile>
</componentProperties>
But then I get
the following:
[INFO] --- hibernate3-maven-plugin:2.2:hbm2java (hbm2java) @ project.persistence ---
[INFO] using configuration task.
[INFO] Configuration XML file loaded: file:/C:/Documents%20and%20Settings/mmm/workspace/project.persistence/target/hibernate3/generated-mappings/hibernate.cfg.xml
12:15:17,484 INFO org.hibernate.cfg.Configuration - configuring from url: file:/C:/Documents%20and%20Settings/mmm/workspace/project.persistence/target/hibernate3/generated-mappings/hibernate.cfg.xml
12:15:19,046 INFO org.hibernate.cfg.Configuration - Reading mappings from resource : package.name/Messages.hbm.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:hibernate3-maven-plugin:2.2:hbm2java (hbm2java) on project project.persistence: Execution hbm2java of goal org.codehaus.mojo:hibernate3-maven-plugin:2.2:hbm2java failed: resource: package/name/Messages.hbm.xml not found
How do I deal with that? Of course I could add:
<outputDirectory>src/main/resources/package/name</outputDirectory>
to
the hbm2hbmxml goal, but I think this is not
the best approach, or is it? Is there a way to keep all
the generated code and resources away from
the src/ folder?
I assume,
the goal of this approach is not to generate any sources into my src/main/java or /resources folder, but to keep
the generated code in
the target folder. As I generally agree with this point of view, I'd like to continue with that eventually executing hbm2dao and packaging
the project to be used as a generated persistence layer component from
the business layer. Is this also what you meant?
