Mike,
Thanks for the quick reply. I still get the same error after replacing the
values in jdbc.properties for username, password, url, and class name both
for jdbc and hibernate.
They now have the actual values instead of the maven macros.
Something else weird is going on. Because I had jetty:
Maven does some property placeholder replacement on the jdbc.properties file
when you run a build. jetty:run-war and tomcat:run-war both invoke a Maven
build in the background, I think jetty:run does not. If you want it all to
work you need to replace the property placeholders in jdbc.properties wi
Folks,
mvn jetty:run fails but mvn tomcat:run-war and mvn jetty:run-war work
correctly.
mvn jetty:run gives an error during startup about a circular
jdbc.driverClassName reference in applicationContext-resources.xml. The
exact error follows.
Please, I love the hot deploy of jetty:run and want t
