I am having a devil of a time getting Eclipse to run my webapp on tomcat with the classpath correct. I have some spring configuration that references property files at classpath:/whatever.properties - these properties files live in my web project at src\main\resources, and I can see that they get deployed to the WEB-INF\classes folder, but they are not picked up. Also, a breakpoint in my custom spring property provider is not hit, even though the code is run (verified through logging).
.project snippet:
<buildSpec>
<buildCommand>
<name>org.maven.ide.eclipse.maven2Builder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.wst.common.project.facet.core.builder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.wst.validation.validationbuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.maven.ide.eclipse.maven2Nature</nature>
<nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
<nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
<nature>org.eclipse.wst.common.project.facet.core.nature</nature>
</natures>
.classpath snippet:
<classpath>
<classpathentry kind="src" path="src/main/java"/>
<classpathentry kind="src" path="src/main/resources"/>
<classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.web.container"/>
<classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.module.container"/>
<classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER">
<attributes>
<attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
</attributes>
</classpathentry>
<classpathentry combineaccessrules="false" kind="src" path="/OtherProject"/>
<classpathentry kind="con" path="org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget/Tomcat v5.5 Server"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk1.5.0_16"/>
<classpathentry kind="output" path="target/classes"/>
</classpath>
org.eclipse.wst.common.component:
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="Web Module">
<wb-resource deploy-path="/" source-path="/src/main/webapp"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/resources"/>
<dependent-module deploy-path="/WEB-INF/lib" handle="module:/resource/OtherProject/OtherProject">
<dependency-type>uses</dependency-type>
</dependent-module>
<property name="context-root" value="WebModule"/>
<property name="java-output-path"/>
</wb-module>
</project-modules>
I have tried with Tomcat's Location (right click the server, select Properties) being in workspace metadata, and also with it living in the Servers project. I have tried using the workspace metadata deployment, letting eclipse take over my tomcat installation, and a custom deployment location. It has worked once - breakpoint hit, properties read - but when I started the server again the next time, it went back to its old ways.
If you need more information, let me know and I'll edit the post ASAP.