[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-737?page=all ]
Max Rydahl Andersen closed HBX-737:
-----------------------------------
Fix Version: 3.2beta8
Resolution: Fixed
i've fixed this issue by instantiating the exporterclass directly in
genericexportertask.
filepattern might be moved up to handle that more generically (especially to allow more
flexible control, eg. via templates)
hbmtemplate tool - GenericExporter omits task attributes when used
with exporterClass
-------------------------------------------------------------------------------------
Key: HBX-737
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-737
Project: Hibernate Tools
Type: Bug
Components: ant
Versions: 3.2beta7
Environment: Hibernate 3.2 cr3, July 7, 2006
Reporter: Michelle Baert
Priority: Minor
Fix For: 3.2beta8
Attachments: CustomExporter-20060825.zip, CustomExporter-20060825.zip,
GenericExporter.java, GenericExporter.zip, GenericExporterTask.java, Patch03.diff,
Work03.diff
I enclose a minimal project with ant build file, and a patch proposal for
GenericExporterTask.
There are 2 custom exporter classes:
- MyExplorer simply extends GenericExporter with nothing else
- My VerboseExplorer is similar but provides log messages.
When run with current version of hibernate-tools, it fails because filepattern has been
lost.
build.xml:66: org.hibernate.tool.hbm2x.ExporterException: File pattern not set on
GenericExporter
When run after patching and jar rebuild, it runs fines.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira