Accepted answer

this should have nothing to do with eclipse and m2eclipse, and optionally for better support - m2e-wtp. also, you don't need copy-dependencies. here are a few possible reasons:

  • you should invoke mvn package (or right-click > maven > package) and obtain a war file - the <packaging> (in the pom) must be war
  • your dependencies should be with the default scope (if they are provided or test they will not be included in the archive)
  • if you are running the project as dynamic web project on a server within eclipse, then you should open the project properties (right click > properties) and select "deployment assembly". there click "add", select "build path entries", and choose "maven dependencies". this will instruct wtp to send the maven dependencies to the server dir.


you want to use the copy-dependencies plugin

see this post and the docs


if you look into your deployment and see that web-inf/lib is empty of your maven dependencies, then ensuring those maven dependencies are in your deployment assembly is crucial as mention in the chosen answer.

however be wary of eclipse then not refreshing everything even with a maven update. if you clean, rebuild and redeploy and still do not see the lib folder being populated try removing and re-adding the application to the server deployments via servers>add and remove.

this unclogged the system for me.


right-click project -> deployment assembly: see if you have the maven dependencies and all others in there. if not, right-click project -> maven -> enable workspace resolution

(maybe then maven -> update project, but then look again into "deployment assembly" and see what you've got.) this solved it (finally!) for me.


on eclipse, select your web project -> right click -> properties -> deployment assembly -> add -> java build path entries -> maven dependencies

with this steps, maven libraries will be included on web-inf/lib when full publish.


i just did maven -> update project worked for me.


check the deployment assembly property of the project. i have seen some mvn eclipse:eclipse generated eclipse projects sometimes have the assets being deployed to the wrong location. from what i can remember the new deployment assembly had some issues with earlier versions of eclipse 3.6 (helios).


right-click project > maven > update maven project > ok fixed it for me


first install maven integration for eclipse wtp (help->eclipse marketplace)

then in your web project's pom.xml just add:


after that just right click the project, maven -> update project, which should automagically add maven dependencies for you in the deployment assembly.

Related Query

More Query from same tag