if it can be useful, setting MySQL5InnoDBDialect as hibernate dialect in the main pom.xml solved the problem for me in a modular struts project, while the datatypeWarning had no effect. bye, Marcello
You might try adding <datatypeWarning> false</datatypeWarning> to your dbunit-maven-plugin configuration. http://mojo.codehaus.org/dbunit-maven-plugin/operation-mojo.html Matt On 10/4/07, WayneFH <[EMAIL PROTECTED]> wrote: > > Actually, I realized that this is coming from dbunit as it loads test > data. > Maybe there is a newer version to use that doesn't use deprecated > functions? > Or a way to disable the warnings? > > -Wayne > > mraible wrote: > > > > I've heard changing to use MySQL5InnoDBDialect solves it, but it > > doesn't solve anything for me locally. > > > > Matt > > > > On 10/4/07, WayneFH <[EMAIL PROTECTED]> wrote: > >> > >> Guys, when running junit tests with maven I get lots of these > deprecation > >> warnings. It has made it hard to find actual errors from hibernate when > >> creating the schema. > >> > >> Anyway to get rid of them? > >> > >> I'm using Basic JSF > >> > >> WARN [main] JDBCExceptionReporter.logWarnings(49) | 'TYPE=storage_ > >> engine' is deprecated; use 'ENGINE=storage_engine' instead > >> > >> Sincerely, > >> Wayne > >> -- -- View this message in context: http://www.nabble.com/Get-rid-of-deprecated-JDBC-warnings-from-Maven--tf4570996s2369.html#a13085142 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
