Hi Johan,
this time i have found/confirmed 2 deficiencies and one more
(philoshophical) question:
I get the error:
org.apache.maven.plugin.MojoExecutionException: Could not get ConfigurationTask.
at
org.codehaus.mojo.hibernate3.HibernateExporterMojo.getConfigurationTask(HibernateExporterMojo.java:162)
at
org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute(Hbm2DDLExporterMojo.java:75)
...
Herei is my config:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>hibernate3-maven-plugin</artifactId>
<executions>
<execution>
<id>export-db-schema</id>
<phase>process-classes</phase>
<goals>
<goal>hbm2ddl</goal>
</goals>
<configuration>
<goals>
<goal>
<name>hbm2ddl</name>
<implementation>configuration</implementation>
</goal>
</goals>
<configurationTaskProperties>
<propertyfile>src/main/config/SYBASE.properties</propertyfile>
<namingstrategy>org.hibernate.cfg.ImprovedNamingStrategy</namingstrategy>
</configurationTaskProperties>
</configuration>
</execution>
</executions>
</plugin>
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 );
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.
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*?
It is quite propable that projects already depend on the only
available version, the SNAPSHOT one.
For instance, i have already 2 such projects, and i'm struggling
(unsuccesfully yet) to preserve my building procedure :-s).
I would kindfully urge all testers to comment on the above issue.
Regards,
Kostis
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
