Description Steve 2011-07-26 04:28:57 EDT

I have a Spring webapp that references a library project, and Workspace Resolution is linking the two.

By default with no exporting of Maven dependencies, when the server starts up I get an error like the following, which is fair enough: 
java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener

In the webapp's build path, when I add Maven Dependencies to the export tab, there is no change. (This may be a bug too)

In the webapp's Deployment Assembly I can add the Maven Dependencies to be deployed to the server, but the above error is replaced with a compile time error:
Classpath Dependency Validator Message
  Invalid classpath publish/export dependency /xxxxx. Project entries not supported.


It seems that if I don't export the dependencies then it won't work, which is pretty much expected. But if I do export the dependencies, then eclipse complains about how the Workspace Resolution is referencing the library project.

Does anyone know a way around this? Any secret XML config I can use?


I am using Eclipse 3.7 with:
m2e - Maven Integration for Eclipse    1.0.0.20110607-2117   
org.eclipse.m2e.feature.feature.group    Eclipse.org - m2e

I have had some success with these features using eclipse 3.6 and the old sonatype m2eclipse, but it was always a bit flaky.


Thanks,

Steve