Missing maven dependencies from deployment assembly
add maven dependencies library to eclipse project
referenced libraries to maven dependencies
maven dependencies folder not showing in eclipse
maven dependency not added to classpath in eclipse
web deployment assembly cannot find entry
tomcat maven dependency eclipse
not able to download maven dependencies in eclipse
I've recently upgraded from eclipse 4.4.2 (Luna) to 4.5 (Mars). My dynamic web project now doesn't include the Maven Dependencies in its deployment assembly "Project->Properties->Deployment assembly".
I can add them manually (using "Project->Properties->Deployment assembly->Add->Java Build Path Entries->Maven Dependencies"), but every time I run "Project->Maven->Update Project Configuration", the Maven Dependencies are removed again.
Note that I run the project using the Apache Tomcat Server within the Eclipse IDE.
I have installed
- m2e 18.104.22.16850526-2032
- m2e-wtp 22.214.171.12450602-1740
333824 – Adding Maven Dependencies to Deployment Assembly , I'm still losing "Maven Dependencies" in Deployment Assemblies. Configuration: m2e 1.6.1; m2e-wtp 1.2.0; Google Plugin 0.0.0.201508031545 Sadly, the default (value=”../”) makes all the Maven’s dependencies failed to deploy. Solution Not a big issue, you still can modify the (value=”../”) to (value=”/WEB-INF/lib”) manually, but it will get override every time you run a Maven build.
can you please try to cleanse setup by following below steps
- disable Maven nature of application :
Right Click Project -> Maven -> Disable Maven Nature
open cmd , go to project location , Run
mvn clean install eclipse:eclipse -Dwtpversion=2.0(This goal just deletes the
.settings/ files/directories. You can also just remove those files (again while the project is open) instead of running
mvn eclipse clean.)
Re-enable the maven nature. (Most of the time, this can be done by right-clicking on the project in question in the package explorer pane, and then choosing
'Configure'-> 'Convert to Maven Project')
other things you can try of
1. reimport project into some other workspace 2. resintall eclipse
if it still didn't solve your problem , most probably you might need to raise
Jira to eclipse team .
Deployment Assembly Omitting Maven Dependencies with m2e-wtp , In Eclipse 3.5 or early version, in order to deployed the Maven dependencies to the correct “/WEB-INF/lib” folder, you have to configure the 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.
I solved the same issue this way:
- Open pom.xml and make Packaging
- Right click the project and select
Will update the project without deleting the Maven Dependencies from Deployment Assembly ; And if the Maven Dependencies is missing the
Maven>Update Project will automatically add it to the project Deployment Assembly
Eclipse : Web Deployment Assembly & Maven dependencies issue , Maven dependency libraries not deploy in Eclipse IDE. See the following Tomcat plugin folder, obviously, the dependency libraries For Eclipse Helios the option is “Deployment Assembly” in the project properties window. Looks like your "Deployment Assembly" is missing the Maven Dependencies being added to the packaging structure of your project. The way this should look is: The way to add that in is: - click on Add - select Java Build Path Entries - select Maven Dependencies - Finish. That should add your Maven Dependencies into WEB-INF/lib.
Maven dependency libraries not deploy in Eclipse IDE, maven dependencies automatically removed from web deployment assembly in The problem is that I need to re-add "Maven dependecies" to the project's deployment assembly each time I add a Thus the missing transitive dependencies. If you're missing dependencies, then check you POM (pom.xml) and make sure they are in there. To verify your dependencies, open the POM editor and select the "Dependency Hierarchy" tab (at the bottom) to get an overview.
I recently had the same issue just like your description above and I got it working this way:
- right-click on project > Maven > Disable Maven Nature
- right-click on project > Configure > Convert to Maven Project
Then call the Maven update project, the Maven dependencies will not disappear from the view of Deployment Assembly again.
maven dependencies automatically removed from web deployment , Inside the Eclipse IDE, we must locate our project. Then: Right click on the project and select Properties . Click on the Deployment Assembly in 1) “Java EE module dependencies” is called “Deployment Assembly” now. 2) U have to choose “Maven Dependencies” in the “Add” dialog, after choosing “Java Build Path Entries”, instead of choosing all libraries independently.
Troubleshooting: Maven Dependency libraries not deployed in , To handle filtering this version of Maven Assembly Plugin uses that it will be uploaded into the repository in the install and deploy phase. If we want to create an assembly binary that includes our project's dependencies, Right click the project and select Maven>Update Project. Will update the project without deleting the Maven Dependencies from Deployment Assembly ; And if the Maven Dependencies is missing the Maven>Update Project will automatically add it to the project Deployment Assembly
Apache Maven Assembly Plugin – Usage, The Eclipse + Maven problem In contemporary Java development, there is a trilogy of unfortunate truths: Eclipse is the most predominant IDE As it turns out, Eclipse does not load files into Tomcat from the Maven “target” directory. Eclipse does its own thing instead, and was oblivious to the Maven kung-fu I had configured. Using Web Deployment Assembly settings to help. Fortunately, someone on Stack Overflow pointed out an Eclipse feature that I had never noticed before.
Using Web Deployment Assembly options to make Eclipse play nice , Check is the maven dependency exist in the Java Build Path Library tab, Deployment Assembly; Check the line /src/main/webapp, if missing However, in the latest Eclipse Helios (3.6), the “Java EE Module Dependencies” is replaced by “Web Deployment Assembly“, which provide more powerful and flexible ways to configure the project packaging structure.
- Do you have the Google plugin for Eclipse installed? If so, you might be running into this issue.
- @cyfur01 No, I don't. But all symptoms seem similar.
- probably same on official issue tracker: bugs.eclipse.org/bugs/show_bug.cgi?id=462591
- Thanks for your response but as I wrote in my question, I tried to add Maven Dependencies using 'Add' in Deployment Assembly. It works but only until I run Maven->Update Project. Then it disappears again...
- @Behnil as in my first point, is
<packaging>war</packaging>there in your
pom.xml? Also the scope of the dependencies ?
- Yes, it is. The application has been working fine for 2 years until I switched to the Eclipse Mars. I think the m2e-WTP ignores it's a maven project or something.
- In my case, the missing
<packaging>war</packaging>was indeed the culprit.
- Why do we need to setup this manually? Shouldn't this be m2e-wtp's job? (configure eclipse projects and m2e to deploy maven projects as it is specified by pom.xml). Maven Update feature should care about adding Maven Dependecies to the Deployment Assembly, I'm point of view. Is something missing or misconfigurated in my pom.xml which breaks m2e-wtp anyhow? It should let me know what it is then, if this is the case. m2e-wtp just seems too buggy for me...
- Actually I clone my GIT repo from scratch as well I create a new workspace directory for the Eclipse. Then I run "Import Maven Projects..." from Git Repositories view. Note that my repo doesn't contain any eclipse related files, so they have been generated - ie they should be fine. Anyway I will try it.
- No, it doesn't help.
- I've just tried. But the Maven Dependencies disappeared again.
- Thanks for your notice. Please check the setting: <installed facet="jst.web" version="3.0"/> inside org.eclipse.wst.common.project.facet.core.xml within .settings folder, the jst.web version should be the same as the web-app version in web.xml header :
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">
- I've found <installed facet="jst.web" version="2.5"/> and yes, it's the same as web-app version in web.xml header.
- Thanks for the hint, I just disabled workspace resolution and the Maven dependencies magically reappeared in the deployment assembly... I could enable again without adverse effect