Hi, I have a sample web app where I am using the dbunit-maven-plugin to load data into a database and the maven-jetty-plugin to run it in jetty. I am issuing the following command to build and deploy the web app. mvn clean install jetty:run. My issue is with some dependencies that I have set as <scope>runtime</scope>. If I comment out the dbunit plugin all works fine - jetty starts up and I can test. When I add the dbunit plugin to the mix, my app has errors when jetty starts up. I looked at the classpath differences between the two runs and I found that all my dependencies marked with scope runtime were not being loaded when the dbunit plugin was used. I removed the runtime scope, with dbunit active and it fixed the problem. My question is why would dbunit stop these dependencies from being loaded at runtime?
Thanks, Todd -- View this message in context: http://www.nabble.com/mvn-jetty%3Arun-and-dbunit-conflict--tp24935948p24935948.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
