Hello Kotis
1) I've seen that there is a bug lurking in Hbm2DDLExporterMojo:75:
Configuration configuration = getConfigurationTask(
getGoal().getName() ).getConfiguration( this );
should become:
Configuration configuration = getConfigurationTask(
getGoal().getImplementation() ).getConfiguration( this );
- Fixed in SVN.
2) The configuration-per-execution is not supported!
I had to use a global element, whcih is awkward,
since i use the hibernate3-plugin 3 times, to produce 3 diffeerent DDL
files for 3 different databases, so i NEED 3 configuration sections.
Actually, the configuration-per-execution pattern might render the
'configuration.goals' node-tree unecessary.
- Can you give me an example of this how you used to do it?
3) I'm wondering whether it is proper behavior to break plugin config
compatiblity so much, considering that *no stable version has ever
been released*?
- Yes, I debated before going this road but because this is a snapshot, this
is the best moment to do such refactoring of the code (I know this is the
second refactoring that this plugin has gone through) since I want to offer
the flexibility that its ANT counterpart has. When I started the plugin it
was based on 2 configurations (annotations was in the works) and now we have
4. So I decided to stick more to mode of programming that the
hibernate-tools uses, so if they add something more or change something
else, it's easy to implement the changes in the MAVEN side. Probably what
I'm going to do is release this as 2.0-SNAPSHOT so these changes won't break
up any build that's working right now, and give opportunity to upgrade their
respective projects if they want to use Annotations or JPA.
Regards
Johann Reyes
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
