So we have a properties file that is in the src and the test resource directories. When we deploy the app to Tomcat running in Eclipse, it takes the test resource files, which is incorrect. Test needs to be a source directory so we can run the tests, but the tests obviously don't run in Tomcat.
Besides using "excludes" in the source, how can you get Eclipse not to deploy the test classes and resource files onto the Tomcat running in Eclipse.
You should have 2 separate source directories - one for the app and one for the tests. If you want to use Maven's standards, they'd be src/main/java and src/test/java.
Normally Eclipse compiles all classes to a single output directory (by default, it's "bin"). However, you can designate individual output directories on a per-source-directroy basis. That will keep the unit test classes out of the WAR.
Customer surveys are for companies who didn't pay proper attention to begin with.
Tim Holloway wrote:You should have 2 separate source directories - one for the app and one for the tests. If you want to use Maven's standards, they'd be src/main/java and src/test/java.
Normally Eclipse compiles all classes to a single output directory (by default, it's "bin"). However, you can designate individual output directories on a per-source-directroy basis. That will keep the unit test classes out of the WAR.
Thanks everything is already configured that way. But for some reason, it still is taking files from the resource directory for tests and putting into the deployment on Tomcat. Tomcat is being run inside Eclipse, so it is all in a tmp0 directory that Eclipse is making and copying files into that directory.
Mark
Brian Mulholland
Ranch Hand
Joined: Mar 12, 2009
Posts: 54
posted
0
Bump. I am having a very similar issue. How did you resolve this?
0
