Argh, more hair pulling! Again it's only happening with eclipse, things are fine when I build with mvn on my unix box at the command line.
And equally maddening; it's suddenly fixed itself. I need a bridge to jump off of. What was happening is my xml config files in src/test/resources were being put in the jars. I finally realized what was happening when I was looking at the console window and saw that logback was using logback-test.xml instead of logback.xml (logback always uses logback-test.xml if one is available). I had changed the log level for org.springframework.beans to DEBUG in logback.xml and it wasn't taking effect; it was still using the WARN level setting in one of the logback-test.xml files. The only thing I changed which seems to have fixed it is in the project properties, under maven, is the box "Goals to invoke after project clean", which has process-test-resources in it, I cleared that for just one of the modules, and then all of the jars stopped getting the test resources. (I was rooting around down in the .metadata/.plugins/org.eclipse.wst.server.core/tmp1/wtpweb folder on my Pc.) I put process-test-resources back and the jars are still not getting the test resources. Talk about voodoo. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
