I had a problem similar to this (java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener), the difference in my case is that the common fix (addi
getting the latest version of the Eclipse IDE for Java EE Developers. As of today, this is Eclipse Mars 4.5. Be sure to select the 64 bit version (if your computer is 64 bit) and to install the latest 64 bit JDK (as of today, this is jdk-8u60).
correctly setting up the JREs in Eclipse by selecting the installed JDK in the Preferences ("Java > Installed JREs").
having up-to-date m2e and m2e-wtp plugins. This is done by going to "Help > Install New Software...", setting this URL for m2e and this URL for m2e-wtp and then installing every proposed software (don't forget to reboot Eclipse after that).
correctly setting up the server in Eclipse: in the "Servers" view, right-click and select "New > Server" and then follow the steps for your specific server; in the end, you will need to add your war through the "Add and Remove..." screen.
cleaning the project in Eclipse by selecting it and going to "Project > Clean".
updating the Maven project by right-clicking the project in Eclipse and going to "Maven > Update Project...".
cleaning the server by right-clicking the server and selecting "Clean" (this depends on your server but there's usually a "Clean" option).
I recommend you do all these steps on a fresh Eclipse install to avoid general caching issues.
As a side note, there are several problems with your POM as-is:
javax.servlet:javax.servlet-api dependency needs to have the provided scope since this dependency is always provided by the web-server at run-time.
javax.servlet:jstl dependency probably doesn't need to have the compile scope and runtime will suffice.
You are declaring a lot of Spring dependencies when you don't need to: they will still be included because they already are transitive dependencies of other artifacts. As such, you can remove the declaration of spring-aop, spring-beans, spring-context, spring-expression, spring-tx and spring-web.
Your testing dependencies are missing the test scope (testng, mockito-all...)
true is unnecessary in your maven-compiler-plugin declaration as this is the default.
The other consideration you might want to fix is that your groupId and artifactId do not follow Maven conventions: prefer using - as separator instead of ..