Argh... You were right about classloader hell.. I was able quite quickly to swap it to use the Hibernate SchemaExportTask with a .properties file. However, attempting to get the right mix of classpath's etc to get SchemaExportTask to work with .cfg.xml configuration file has been a very frustrating day! I was able to create a build.xml that worked with a .cfg.xml and .properties file, but converting that into the plugin.jelly just never worked.
I have been able to add a src/plugin-test project that validates things work, which pretty much means only with a .properties file. I tried writing a unit test to load up the SchemaExportBean and use it via a .properties or .cfg.xml but no joy. So, at this point, I do have my nice little /src/plugin-test to contribute. However, is there any feeling on committing the Ant task instead of the custom integration or not? Right now the Ant task version does the same as the custom integration, and neither seems to deal with a .cfg.xml configuration file. Opinions? Eric > -----Original Message----- > From: Maczka Michal [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 23, 2004 3:12 PM > To: 'Maven Developers List' > Subject: RE: Hibernate plugin use Ant task instead of custom integration > > > > > -----Original Message----- > > From: Eric Pugh [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 23, 2004 2:42 PM > > To: Maven-Dev > > Subject: Hibernate plugin use Ant task instead of custom integration > > > > > > Hi all, > > > > I noticed a patch a while ago to the list from Konstantin > > Shaposhnikov which > > converted the Hibernate plugin to use the SchemaExportTask that is now > > available from the main Hibernate jar. I am going to update > > to using the > > Ant task as the existing interface to SchemaExport hasn't > > kept up with the > > various properties now available to SchemaExport (like using > > a .cfg.xml > > configuraiton file instead of .properties). This will > > hopefully reduce > > maintaince as well. > > > > If anyone sees this as a bad idea, please holler! > > > > As for me (I started this plugin) - please feel free to do > whatever you want > with it ... > > I didn't feel that it is the right idea to use ant tasks as I had > some nasty > problems with classloaders. > For m2 the preferred way of writing plugins is using Java and so called > Maven Pojos (Mojos). > > > regards > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
