Have you tried declaring your driver as a dependency instead of as an
extension?
-allan
bkbonner wrote:
Max, I did do this, which is why I posted my original msg. Thanks for
replying, just the same.
I realized what was happening. The driver URL syntax had changed in the new
driver version.
I wanted to rule out that there wasn't anything special about the artifact.
Lo and behold, it's just a regular JDBC driver library as you correctly
stated.
Brian
--
View this message in context:
http://www.nabble.com/hibernate3-extension---No-Suitable-Driver-t1838389.html#a5019392
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
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]
