Also, "ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader" seems to appear in the velocity log on each build. The file does not appear to be present in either jar.
One final thing: running torque:create-db, torque cannot find my JDBC driver, which is on my project's classpath.
All of these issues seem to be related - anyone see the smoking gun here? I have torque.useClasspath=true, using Torque Maven plugin, and I am using a recent snapshot of Velocity.
Thanks in advance,
Gabe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
