I have a dynamic web application that I've converted to a maven project in Spring Toolsuite (Eclipse, basically.) The project now has a pom.xml file, but the Java Build Path no longer has the jars I used to use because maven is supposed to handle the dependencies. I put the dependencies in the pom like this:
<dependencies>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>(,1.0]</version>
</dependency>
</dependencies>
and I included a repository like so:
<repositories>
<repository>
<id>maven2-repository.dev.java.net</id>
<name>Java.net Repository for Maven</name>
<url>http://download.java.net/maven/2/</url>
<layout>default</layout>
</repository>
</repositories>
Still, the dependency isn't resolved and my servlets aren't working. Why isn't my converted Maven project making dependency management any easier? Why aren't the servlet imports working, more specifically?
You can add the dependencies to the deployment by:
You can add the dependencies to the build path by:
You shouldn't be importing the servlet dependencies via Maven though, you should be pointing at your servers runtime. You can configure this by: