Hello Peter
For the jdbc drivers, you need to use it as an extension for it to be
available to hibernate as described here:
http://mojo.codehaus.org/hibernate3-maven-plugin/howto.html
Regards
Johann Reyes
-Original Message-
From: Peter L. Berghold [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 8:38 AM
To: users@maven.apache.org
Subject: classpaths and more hibernate foo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK,
So I've gotten the hibernate plug-in doing some stuff for me. I've got
it creating POJOS from foo.hbm.xml files and I have it creating
hibernate.cfg.xml from my database.properties files and the various
foo.hbm.xml files.
Groovy.
So now I want to create my schema, I invoke
mvn hibernate:schema-export
I and see lots of spew and somewhere buried in there is a message saying:
java.sql.SQLException: No suitable driver
What? That's crazy talk!
I check my pom.xml file and sure enough I have
dependency
groupIdpostgresql/groupId
artifactIdpostgresql/artifactId
version8.1-404.jdbc3/version
scopecompile/scope
/dependency
among other dependencies that I feel my project has. I do some reading
and I read on the maven website under scope the following:
Compile dependencies are available in all classpaths.
OK: I'm thick-headed... what am I missing here? Shouldn't the postgres
JDBC drivers be available to the schema export task? What's the magic
foo that makes it so?
- --
Peter L. Berghold [EMAIL PROTECTED]
Those who fail to learn from history are condemned to repeat it.
AIM: redcowdawgYahoo IM: blue_cowdawg ICQ: 11455958
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
iD8DBQFEKTw2UM9/01RIhaARAhVAAJ0ewh45+mg8VBxrIU7nGWL60wLMmQCgrY31
7ZJpQ84oDwFsW3LE7ZUi2aM=
=UeEJ
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
