Aug 28th, 2010, 01:01 PM
Nope. That won't solve the problem. You are assuming that I'm using STS distro of Eclipse.
I am using Helios + STS from the update site. As it turns out, the base distro of Eclipse does not contain the same Maven plugins as the STS distro. The default plugin for Eclipse does not seem to honor the scope of a dependency, therefore it always deploys jsp-api even if you tell it that it is "provided". This causes problems with Tomcat (or compatible servers) at runtime.
The solution was to install "Maven Integration for Eclipse (Extras) 0.10.0.". This added the missing parts to Maven. I also installed Maven 2.2.1 on my machine and told Eclipse to use that Maven instead of the embedded one.
This solved the problem about deployments. The <resources> element will hopefully be resolved in a future STS release.
Aug 30th, 2010, 09:31 AM
You are right. I was assuming you are using STS.
Sep 15th, 2010, 01:57 PM
Torczuk got it
Torczuk gave me the right idea. From within the project properties/JEE Module Dependencies unselect both libraries mentioned by him and it'll work. @Torczuk: Thanks a lot! Apparently, Eclipse Maven Integration doesn't respect the Maven scope yet. Thus the manual step
Nov 16th, 2010, 03:04 AM
Another way to get it run smoothly in Eclipse Helios is to generate a new Project Configuration with mvn (the console tool, not the plugin).
First, delete the eclipse configuration files .classpath, .project and the .settings directory, then execute mvn eclipse:eclipse -Dwtpversion=2.0 in the project directory.
In Eclipse, then right-click the project and select "refresh". E voilá, it will run perfectly. If you take a look at Deployment Assembly in the project configuration now, you will see, that the two jars that are provided are not included anymore.
I use this trick for other projects too, since the eclipse maven plugin still has some flaws and often fails to make a proper eclipse configuration.