Hello David, You were receiving before that error about the annotationconfiguration?? Also to use full paths useBasedir should be set to false, not true
Regards Johann Reyes -----Original Message----- From: dbernard [mailto:[EMAIL PROTECTED] Sent: Friday, November 03, 2006 7:23 PM To: [email protected] Subject: Re: [mojo-dev] hibernate3 maven2 plugin does not accept full path names - FIX BROKEN? Johann, Snapshot [DEBUG] maven-hibernate3-jdk15: resolved to version 1.0-20061103.175439-6 from repository snapshots I am getting: With following configuration: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>hibernate3-maven-plugin</artifactId> <configuration> <hibernate> <!-- Same with or without this line --> <configurationClass>org.hibernate.cfg.AnnotationConfiguration</ configurationClass> <propertyFile>../src/test/resources/ database.properties</propertyFile> <configurationFile>src/main/resources/ hibernate.cfg.xml</configurationFile> <!-- Same with or without this line <useBasedir>true</useBasedir> --> </hibernate> </configuration> <executions> <!-- Generate DB schema from annotated classes identified in hibernate.cfg.xml --> <execution> <id>Generate DB Schema (Not used)</id> <phase>pre-integration-test</phase> <goals> <goal>hbm2ddl</goal> </goals> <configuration> <outputDirectory> <hbm2ddl>${buildDirectory}/hibernate3</hbm2ddl> </outputDirectory> <outputFile>create-db.sql</outputFile> <drop>false</drop> <update>false</update> </configuration> </execution> Getting: DEBUG] Configuring mojo 'org.codehaus.mojo:hibernate3-maven-plugin: 1.0-SNAPSHOT:hbm2ddl' --> [DEBUG] (f) delimiter = ; [DEBUG] (f) drop = false [DEBUG] (f) format = true [DEBUG] (f) outputFile = create-db.sql [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) update = false [DEBUG] -- end configuration -- [INFO] [hibernate3:hbm2ddl {execution: Generate DB Schema (Not used)}] log4j:WARN No appenders could be found for logger (org.hibernate.cfg.Environment). log4j:WARN Please initialize the log4j system properly. [DEBUG] using org.hibernate.cfg.Configuration [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] An AnnotationConfiguration instance is required to use <mapping class="com.silverbrookresearch.qaco.memjet_supervisor.model.users.User"/ > [INFO] ------------------------------------------------------------------------ [DEBUG] Trace org.hibernate.MappingException: An AnnotationConfiguration instance is required to use <mapping class="com.silverbrookresearch.qaco.memjet_supervisor.model.users.User"/ > at org.hibernate.cfg.Configuration.parseMappingElement (Configuration.java:1524) at org.hibernate.cfg.Configuration.parseSessionFactory (Configuration.java:1479) at org.hibernate.cfg.Configuration.doConfigure (Configuration.java:1458) at org.hibernate.cfg.Configuration.doConfigure (Configuration.java:1432) at org.hibernate.cfg.Configuration.configure (Configuration.java:1386) at org.codehaus.mojo.hibernate3.configuration.AbstractConfigHibernate.getCo nfiguration(AbstractConfigHibernate.java:66) at org.codehaus.mojo.hibernate3.HibernateExporterMojo.getConfiguration (HibernateExporterMojo.java:108) at org.codehaus.mojo.hibernate3.exporter.SchemaExportMojo.doSchemaExport (SchemaExportMojo.java:63) at org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute (Hbm2DDLExporterMojo.java:56) at org.codehaus.mojo.hibernate3.HibernateExporterMojo.execute (HibernateExporterMojo.java:59) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) On 04/11/2006, at 10:50 AM, Johann Reyes wrote: > Hello David > > I've already deployed the snapshot, so if you run your goal with > the -U > parameter, it should update your version with the latest one. > > Regards > > Johann Reyes > > -----Original Message----- > From: dbernard [mailto:[EMAIL PROTECTED] > Sent: Friday, November 03, 2006 5:40 PM > To: [email protected] > Subject: Re: [mojo-dev] hibernate3 maven2 plugin does not accept > full path > names > > Thanks Johann, > > That should do the trick. > > When do you think that the change will turn up in the snapshot > version or should I build from SCM? > > David > > On 04/11/2006, at 4:58 AM, Johann Reyes wrote: > >> Hello David >> >> I just added a new property "useBasedir" that you'll have to set to >> false >> for the plugin to know not to use the project basedir for those two >> paths. >> >> Ex. >> >> <configuration> >> <hibernate> >> <useBasedir>false</useBasedir> >> </hibernate> >> </configuration> >> >> Regards >> >> Johann Reyes >> >> -----Original Message----- >> From: dbernard [mailto:[EMAIL PROTECTED] >> Sent: Friday, November 03, 2006 3:17 AM >> To: [email protected] >> Subject: [mojo-dev] hibernate3 maven2 plugin does not accept full >> path names >> >> Hi, >> >> The hibernate3 plugin does not seem to support full path names for >> the location of the hibernate.cfg.xml or database.property files. >> >> May SCM system needs me to use a temporary directory during testing >> and so I can't use "target" as output directory but need >> to use a /tmp directory. The debug out shows the past property but >> the plugin reports: >> >> >> [DEBUG] Configuring mojo 'org.codehaus.mojo:hibernate3-maven-plugin: >> 1.0-SNAPSHOT:schema-update' --> >> [DEBUG] (f) propertyFile = ../src/test/resources/ >> database.properties >> [DEBUG] (f) configurationFile = /tmp/15337/model-hibernate/target/ >> classes/hibernate.cfg.xml >> [DEBUG] (f) hibernate = >> org.codehaus.mojo.hibernate3.configuration.jdk15.ConfigHibernateImpl@ >> 1 >> 9b >> 808a >> [DEBUG] (f) outputDirectory = >> org.codehaus.mojo.hibernate3.configuration.jdk15.ConfigOutputDirector >> y >> Im >> [EMAIL PROTECTED] >> [DEBUG] (f) project = [EMAIL PROTECTED] >> [DEBUG] -- end configuration -- >> [INFO] [hibernate3:schema-update {execution: Generate and Apply DB >> Schema}] >> [DEBUG] using org.hibernate.cfg.AnnotationConfiguration >> [INFO] No hibernate configuration file loaded: None specified. >> [INFO] Configuration Properties file loaded: /data0/nobackup/home/ >> dbernard/oss.1.0.C021/12-QAInfrastructure/17-Memjet_Supervisor/04- >> Software_Modules/model-hibernate/../src/test/resources/ >> database.properties >> >> Any suggested work around ? >> >> David Bernard >> >> --------------------------------------------------------------------- >> 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 >> > > > --------------------------------------------------------------------- > 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 > --------------------------------------------------------------------- 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
