Hello Kostis:
1) Try this and let me know how it goes.
<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>
</execution>
<execution>
<id>export-SYBASE</id>
<phase>site</phase>
<goals>
<goal>hbm2ddl</goal>
</goals>
<configuration>
<configurationTaskProperties>
<drop>true</drop>
<export>false</export>
<outputfilename>SYBASE.frepor-ddl.sql</outputfilename>
<propertyfile>src/main/config/SYBASE.properties</propertyfile>
</configurationTaskProperties>
</configuration>
</execution>
<execution>
<id>export-MYSQL</id>
<phase>site</phase>
<goals>
<goal>hbm2ddl</goal>
</goals>
<configuration>
<configurationTaskProperties>
<drop>true</drop>
<export>false</export>
<outputfilename>MYSQL.frepor-ddl.sql</outputfilename>
<propertyfile>src/main/config/MYSQL.properties</propertyfile>
</configurationTaskProperties>
</configuration>
</execution>
</executions>
<configuration>
<configurationTaskProperties>
<drop>true</drop>
<export>false</export>
<outputfilename>frepor-ddl.sql</outputfilename>
<propertyfile>src/main/config/database.properties</propertyfile>
<namingstrategy>org.hibernate.cfg.ImprovedNamingStrategy</namingstrategy>
</configurationTaskProperties>
</configuration>
<dependencies>
<dependency>
<groupId>org.jvnet.hyperjaxb2</groupId>
<artifactId>hyperjaxb2-shared</artifactId>
<version>0.5.1</version>
</dependency>
</dependencies>
</plugin>
-----Original Message-----
From: Kostis Anagnostopoulos [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 6:07 AM
To: [email protected]
Subject: Re: [mojo-dev] [hibernate3-maven-plugin] Testers needed
Hi Johann,
On 11/30/06, Johann Reyes <[EMAIL PROTECTED]> wrote:
> Hello Kotis
>
> ...
>
> 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?
Be my guest to my old pom:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>hibernate3-maven-plugin</artifactId>
<executions>
<execution>
<id>export-db-schema</id>
<phase>process-classes</phase>
<goals>
<goal>schema-export</goal>
</goals>
</execution>
<execution>
<id>export-SYBASE</id>
<phase>site</phase>
<goals>
<goal>schema-export</goal>
</goals>
<configuration>
<hibernate>
<propertyFile>src/main/config/SYBASE.properties</propertyFile>
</hibernate>
<outputFile>SYBASE.frepor-ddl.sql</outputFile>
<drop>true</drop>
</configuration>
</execution>
<execution>
<id>export-MYSQL</id>
<phase>site</phase>
<goals>
<goal>schema-export</goal>
</goals>
<configuration>
<hibernate>
<propertyFile>src/main/config/MYSQL.properties</propertyFile>
</hibernate>
<outputFile>MYSQL.frepor-ddl.sql</outputFile>
<drop>true</drop>
</configuration>
</execution>
</executions>
<configuration>
<hibernate>
<namingStrategy>org.hibernate.cfg.ImprovedNamingStrategy</namingStrategy>
<propertyFile>src/main/config/database.properties</propertyFile>
</hibernate>
<outputFile>frepor-ddl.sql</outputFile>
<drop>true</drop>
</configuration>
<dependencies>
<dependency>
<groupId>org.jvnet.hyperjaxb2</groupId>
<artifactId>hyperjaxb2-shared</artifactId>
<version>0.5.1</version>
</dependency>
</dependencies>
</plugin>
2) Yep, that's the problem with sandbox, can't make a release without doing
an official release first. Either way, most likely people that are using now
the plugin they are pointing to the snapshot version so I guess the best
step to follow is just leave SNAPSHOT-1 as it is. It's really well stable
for non-jdk15 hibernate projects, that's why the bugs that I have been
getting lately are more from the jdk15 part of hibernate, and that's why
this change needed to be implemented.
3) On that personal note, first I apologize for such a mistake from my part,
and I have to say really no special meaning, just you met let's say my
curse, which I believe is called dyslexia. Not intended to skip a letter but
I tend to do that a lot along with flipping and replacing characters, a good
example would be during a good time of development of the plugin the hbm2ddl
goal was called "hbm2dll". And I didn't noticed my error until someone
pointed that out. LOL
Once again my apologies for my error, and let me know how it goes.
Regards
Johann Reyes
> 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.
I can see the merits of the new configuration, and i agree with you
that it is superior to the old functionality.
I also agree with the move to 2.0-SNAPSHOT and i would augment it with
2 actions:
a) Fork old 1.0-SNAPSHOT svn revison (based on rev 2536?), and
b) release 1.0. (i don't know whether you can use the sandbox for a
release)
---
In a more personal and funny note, Johann,
I see that you preffer the "Kotis" over my proper name, "Kostis"
(a variant of "Kostas", from "Konstantine", from latin "constant").
I'm curious whether you know the word "kotis" to have a certain meaning?
Regards,
Kostis
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
