Are you using war overlays or just expect the war classes, packaged as a jar, to be deployed in the other war's web-inf/lib? First case *should* work, 2nd case (using the <attachClasses> and <classifier>classes</classifier> combo) is not supported due to m2e not supporting classifiers when workspace resolution is active.
http://wiki.eclipse.org/M2E-WTP_FAQ#How_do_I_add_my_web_project_classes_to_another_project.27s_classpath.3F might help getting the classpath working in the workspace but not during deployment. Your best solution would be to move the "common" classes to a separate maven module, with jar packaging, referenced by both wars. If you can't do that, you can still disable workspace resolution (right click on project Maven -> Disable Workspace Resolution), but then, you'll have to install your war dependency to your local repo whenever you modify its classes. HIH Fred Bricon On Thu, Jun 14, 2012 at 9:46 AM, Harald Wellmann < [email protected]> wrote: > I have two WAR projects foo and bar where foo depends on the classes > artifact of bar. When running foo on Tomcat using Eclipse WTP + m2e + > m2e-wtp, the bar-classes.jar is missing from WEB-INF/lib. > > Does m2e-wtp support this scenario at all? If so, what could be > missing in my setup? > > Best regards, > Harald > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > -- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
