Re: hibernate3 maven2 plugin problem

2008-07-21 Thread René Johannes
>Caused by: java.sql.SQLException: No suitable driver

Set Driver_class in hibernate.properties ?

hibernate.connection.driver_class com.mysql.jdbc.Driver



- Original Message - 
From: "Renu Gupta" <[EMAIL PROTECTED]>
To: "Maven Users List" 
Sent: Monday, July 21, 2008 9:41 AM
Subject: hibernate3 maven2 plugin problem


Hi,
While using hibernate3 maven2 plugin. I m getting this error:

[INFO] [hibernate3:hbm2ddl]
[DEBUG] Setting context classloader for plugin to: 
/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL 
PROTECTED]/thread:main (instance is: 
ClassRealm[/plugins/org.codehaus.mojo:hibernate3-maven-plugin:[EMAIL 
PROTECTED]/thread:main, parent: ClassRealm[plexus.core, parent: null]])
13:00:20,800  INFO org.hibernate.cfg.Environment - Hibernate 3.2.0.cr5
13:00:20,800  INFO org.hibernate.cfg.Environment - loaded properties from 
resource hibernate.properties: 
{hibernate.dialect=org.hibernate.dialect.MySQLDialect, 
hibernate.bytecode.use_reflection_optimizer=false}
13:00:20,800  INFO org.hibernate.cfg.Environment - Bytecode provider name : 
cglib
13:00:20,815  INFO org.hibernate.cfg.Environment - using JDK 1.4 
java.sql.Timestamp handling
13:00:20,894  INFO org.hibernate.cfg.Configuration - configuring from file: 
hibernate.cfg.xml
[DEBUG] basedir: F:\Documents and 
Settings\rvgupta\eclipsemavenworkspace\trial-plugin
[INFO] Configuration XML file loaded: F:\Documents and 
Settings\rvgupta\eclipsemavenworkspace\trial-plugin\src\main\resources\hibernate.cfg.xml
13:00:21,050  INFO org.hibernate.cfg.JDBCMetaDataConfiguration - Ignoring null 
mapping
13:00:21,050  INFO org.hibernate.cfg.Configuration - Configured SessionFactory: 
null
[INFO] src/main/resources/database.properties not found within the project. 
Trying absolute path.
[INFO] No hibernate properties file loaded.
13:00:21,097  INFO org.hibernate.connection.DriverManagerConnectionProvider - 
Using Hibernate built-in connection pool (not for production use!)
13:00:21,097  INFO org.hibernate.connection.DriverManagerConnectionProvider - 
Hibernate connection pool size: 20
13:00:21,097  INFO org.hibernate.connection.DriverManagerConnectionProvider - 
autocommit mode: false
13:00:21,097  INFO org.hibernate.connection.DriverManagerConnectionProvider - 
using driver: com.mysql.jdbc.Driver at URL: 
jdbc:mysql://localhost/firsthibernate
13:00:21,112  INFO org.hibernate.connection.DriverManagerConnectionProvider - 
connection properties: {user=root, password=}
13:00:21,112  WARN org.hibernate.cfg.SettingsFactory - Could not obtain 
connection metadata
java.sql.SQLException: No suitable driver
  at java.sql.DriverManager.getConnection(DriverManager.java:545)
  at java.sql.DriverManager.getConnection(DriverManager.java:140)
  at 
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
  at 
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:76)
  at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1929)
  at 
org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC(JDBCMetaDataConfiguration.java:38)
  at 
org.codehaus.mojo.hibernate3.configuration.JDBCComponentConfiguration.doConfiguration(JDBCComponentConfiguration.java:67)
  at 
org.codehaus.mojo.hibernate3.configuration.AbstractComponentConfiguration.getConfiguration(AbstractComponentConfiguration.java:37)
  at 
org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute(Hbm2DDLExporterMojo.java:87)
  at 
org.codehaus.mojo.hibernate3.HibernateExporterMojo.execute(HibernateExporterMojo.java:140)
  at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577)
  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
  at 
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
  at 
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
  at 
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903)
  at 
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
13:00:21,144  INFO org.hibernate.dialect.Dialect - Using dialect: 
org.hibernate.dialect.MySQLDialect
1

Release Prepare

2008-05-22 Thread René Johannes
Hi,

Using the maven-release-plugin : release:prepare

We use maven embedder in a project, when running the goal release:prepare then
the version numbers are changed and now the maven embedder does not have the 
correct
version number. 

The new version number is not installed during process but maven embedder wants 
to use it.

Please help.