added a comment - - edited
What changed with WTP 2.0 IMHO is the way J2EE module dependencies are declared. They no longer are declared inside .settings/org.eclipse.wst.common.component, but as a classpath entry attribute in .classpath instead.
So, currently (for WTP 1.5) there is an entry in .settings/org.eclipse.wst.common.component created, like
<dependent-module deploy-path="/WEB-INF/lib" handle="module:/classpath/var/M2_REPO/org/springframework/spring-core/2.0.5/spring-core-2.0.5.jar">
For WST 2.0 the following entry must be created in .classpath instead:
<classpathentry kind="var" path="M2_REPO/org/springframework/spring-core/2.0.5/spring-core-2.0.5.jar">
<attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
The issue of supporting classpath entry attributes is also relevant for
Currently after an "mvn eclipse:eclipse" when using WTP 2.0 I have to manually:
1. Drop the dependency entries from .settings/org.eclipse.wst.common.component (either by unchecking them via Eclipse "J2EE Moduie" GUI, or by editing the file directly).
2. Add the "org.eclipse.jst.component.dependency" attribute to the classpath entries in .classpath (again by checking them via Eclipse "J2EE Moduie" GUI, or by editing the file directly).
MECLIPSE-270 related) Add my spring-aspects.jar to the AspectJ Path (via GUI or editing .classpath)