Missing Maven dependencies in Eclipse project

Question

We have a project set up with maven for resolving dependancies  It usually works fine  but now I am trying to compile and run it on a new PC and I have problem with missing dependencies in Eclipse   What is funny is that if I run  mvn package  in console or in eclipse  it works fine and even produces war containing all necessary jars  Only Eclipse complains with  The project was not built since its build path is incomplete  Cannot find the class file for org slf4j Logger      If I compare the project with some other computer  where project works fine   I notice that there are quite a few libraries missing under  Maven dependencies  listing in Eclipse  Eventhough they are in the packaged war and they can be found also under repository folder   So  the jar-s are there just Eclipse won t list them all under  Maven dependencies   What can I do   Computer is running on Windows 7 with 64bit java  amp  eclipse

User · Answer

I could solve the error by  1  Right click  your maven project  -  maven -  maven install  After successful installation  2   Right click  your maven project  -  maven -  update project  And the whole error of maven got solved

User · Answer

My Project was just screwed up  Here is how I fixed it for Eclipse Indigo x64  J2EE 3 7 3     Deleted my POM file  backedup of course   Project Context Menu   Maven   Disable Maven Nature  Deleted the project  but not contents on disk   Re-imported as Import   General   Existing Project  Project Context Menu   Configure   Convert to Maven Project     Accept defaults from Maven wizard  Overwrite POM with your backedup POM   Now you have Maven Dependencies folder   Maven Update Clean for good measure    Hope that helps someone

User · Answer

So many answers  You see  there could be many reasons  why this is not working  as expected  In my case  I also did not realize the  - Tag around my dependencies  facepalm  Example        lt dependencyManagement gt       lt dependencies gt           lt dependency gt               lt groupId gt org slf4j lt  groupId gt               lt artifactId gt slf4j-log4j12 lt  artifactId gt               lt version gt   org slf4j version  lt  version gt           lt  dependency gt       lt  dependencies gt   lt  dependencyManagement gt      this only DEFINES the dependency for this and all subprojects with desired version  This is  what it e g  should look like in the master-POM  To really use the lib in THIS current project  you have too add the depency as following        lt dependencyManagement gt       lt dependencies gt           lt dependency gt               lt groupId gt org slf4j lt  groupId gt               lt artifactId gt slf4j-log4j12 lt  artifactId gt               lt version gt   org slf4j version  lt  version gt           lt  dependency gt       lt  dependencies gt   lt  dependencyManagement gt    lt dependencies gt       lt dependency gt           lt groupId gt org slf4j lt  groupId gt           lt artifactId gt slf4j-log4j12 lt  artifactId gt       lt  dependency gt   lt  dependencies gt      NOW it will provide the lib in THIS current project

User · Answer

I had a similar issue and have tried all the answers in this post  The closest I had come to resolving this issue was by combining the Joseph Lust and Paul Crease solutions  I added the backed up pom xml file after deleting and reimporting the project  and nothing showed up until I deleted the dependency management tag in the pom xml and magically the dependencies folder was there   However  it broke up the child POM s since they need the parent pom xml dependency management to function  and as a result my MVN was not functioning properly on the project either from Eclipse or the command line  giving a broken pom xml error   The last solution if all fails  is to manually import the  jar files needed by your project  Right click the project Properties -  Java Build Path -  Libraries and Add external Jar   If your MVN is working correctly from the command line and you have done a successful build on the project  you will have all the repos needed in your  m2 repository folder  Add all the external jars mentioned in your dependencies tag of pom xml and you will see a referenced library section in your Eclipse  with all the pesky red errors gone   This is not the optimal solution  but it will let you work in Eclipse without any errors of missing dependencies  and also allow you to build the Maven project both from Eclipse and command line

User · Answer

I m also new to Eclipse  and I ve been having a similar problem where Eclipse just won t recognize an import statement  even though all signs point to the dependency having been successfully downloaded   You should check that your dependency file has actually been downloaded by going to the command line and typing  mvn dependency tree  If you see your package there  then but Eclipse doesn t acknowledge it  the thing that works for me  sometimes  is to go to the terminal  cd into the project folder  and type  mvn eclipse clean then mvn eclipse eclipse  Finally refresh project in eclipse  I don t know why this works  and sometimes it doesn t work once  then doing it again does work    so worth a try

User · Answer

None of the solutions above worked for me  so this answer is for anyone else in my situation  I eventually found the problem myself  and a different solution  The pom xml file contained a dependencyManagement tag that wrapped the dependencies  and M2Eclipse would not add the Maven Dependencies folder when this was present  So  I removed this tag  then carried out the solution offered by Ualter Jr   and Eclipse immediately added the missing folder

User · Answer

I had this issue for dependencies that were created in other projects   Downloaded thirdparty dependencies showed up fine in the build path  but not a library that I had created   SOLUTION  In the project that is not building correctly    Right-click on the project and choose Properties  and then Maven   Uncheck the box labeled  Resolve dependencies from Workspace projects  Hit Apply  and then OK  Right-click again on your project and do a Maven- Update Snapshots  or Update Dependencies    And your errors should go away when your project rebuilds  automatically if you have auto-build enabled

User · Answer

My answer is similar to that of  JerylCook  find another  classpath file in a working Maven project  edit your bad ones as that good working ones  The key is to add    lt attributes gt       lt attribute name  maven pomderived  value  true   gt   lt  attributes gt    in every  lt classpathentry gt  of type con and src  Don t forget to change  lt classpathentry        gt  to  lt classpathentry     gt xxx lt  classpathentry gt    At last  update the maven project and reinstall rebuild in maven

User · Answer

update the  classpath to below will work every time    lt  xml version  1 0  encoding  UTF-8   gt   lt classpath gt       lt classpathentry kind  src  output  target classes  path  src main java  gt           lt attributes gt               lt attribute name  optional  value  true   gt               lt attribute name  maven pomderived  value  true   gt           lt  attributes gt       lt  classpathentry gt       lt classpathentry kind  src  output  target test-classes  path  src test java  gt           lt attributes gt               lt attribute name  optional  value  true   gt               lt attribute name  maven pomderived  value  true   gt           lt  attributes gt       lt  classpathentry gt       lt classpathentry excluding      kind  src  output  target test-classes  path  src test resources  gt           lt attributes gt               lt attribute name  maven pomderived  value  true   gt           lt  attributes gt       lt  classpathentry gt       lt classpathentry excluding      kind  src  output  target classes  path  src main resources  gt           lt attributes gt               lt attribute name  maven pomderived  value  true   gt           lt  attributes gt       lt  classpathentry gt       lt classpathentry excluding  WEB-INF   kind  src  path  src main webapp   gt       lt classpathentry kind  con  path  org eclipse m2e MAVEN2 CLASSPATH CONTAINER  gt           lt attributes gt               lt attribute name  maven pomderived  value  true   gt               lt attribute name  org eclipse jst component dependency  value   WEB-INF lib   gt           lt  attributes gt       lt  classpathentry gt       lt classpathentry kind  con  path  org eclipse jdt launching JRE CONTAINER   gt       lt classpathentry kind  output  path  target classes   gt   lt  classpath gt

User · Answer

I have the same issue as you  after trying all the clean  update and install and there was still missing artifacts  Problem for me is that profiles are not being applied  Check in your  m2 settings xml and look for  lt activeProfile gt   Go back to your project  right click under properties -  maven and enter your Active Maven Profiles  All the missing artifacts were resolved

User · Answer

I got this error when had an error in Pom    Run mvn eclipse eclipse command on console to check that pom is parsable or not  If not parsable search for the error

User · Answer

I also encountered this problem  It confused me several hours  I tried many of solutions which were suggested in this topic  At last  I found it was due to the Java Element Filters

User · Answer

In Eclipse STS if  Maven Dependencies  disappears it  you have to check and fix your pom xml  I did this  twice  and I resolved it  It was not a dependencies issue but a String generated and moved in a position random in my pom xml

User · Answer

For the following steps worked in my case   1  On eclipse  right click on the desired project Maven -  Disable Maven Nature   2  Right click again then go to Properties  Delete every evidence of external Maven dependency leaving only JRE System Library   3 Right click one more time on the project then go to Configure -  Convert to Maven Project

User · Answer

So I m about 4 or 5 years late to this party  but I had this issue after pulling from our repo  and none of the other solutions from this thread worked out in my case to get rid of these warnings errors   This worked for me   From Eclipse go to to Window -  Preferences -  Maven  expand  -  Errors Warnings  The last option reads  Plugin execution not covered by lifecycle configuration  - use the drop-down menu for this option and toggle  Ignore   then Apply  then OK   At  Requires updating Maven Projects  prompt say OK    Further Info    This may not necessarily  fix  the underlying issue s   and may not qualify as  best practice  by some  however it should remove supress these warnings from appearing in Eclipse and let you move forward at least  Specifically - I was working with Eclipse Luna Service Release 1  4 4 1  w  Spring Dashboard  amp  Spring IDE Core  3 6 3   and m2e  1 5  installed  running on Arch Linux and OpenJDK 1 7  I imported my project as an existing maven project and selected OK when warned about existing warnings errors  to deal with them later       Sorry  I m not a designer  but added picture for clarity

User · Answer

This is how I solved it   Window- Preferences  Maven- User Settings  Click on  open file  in resulting window  or just edit settings xml with an external text editor like Notepad  Make sure localRepository  which is displayed in this window  is correct   I had a typo in my file    Once you have corrected settings xml  click on Update Settings  which is on this same Preferences- Maven- User Settings screen    Now rebuild  and it will install the latest JAR s in the correct location

User · Answer

the whole project looked weird in eclipse  maven dependencies folder were missing  it showed some types as unknown  but I was able to build it successfully in maven  What fixed my issue was adding gen folder to source path on project build path    Probably this is similar to this Android  FBReaderJ gen already exists but is not a source folder  Convert to a source folder or rename it

User · Answer

For me it was sufficient add a buildCommand  org eclipse m2e core maven2Builder  and a nature  org eclipse m2e core maven2Nature  in the  project file  like this    lt  xml version  1 0  encoding  UTF-8   gt   lt projectDescription gt       lt name gt iText lt  name gt       lt comment gt  lt  comment gt       lt projects gt       lt  projects gt       lt buildSpec gt           lt buildCommand gt               lt name gt org eclipse jdt core javabuilder lt  name gt               lt arguments gt               lt  arguments gt           lt  buildCommand gt           lt buildCommand gt               lt name gt org eclipse m2e core maven2Builder lt  name gt               lt arguments gt               lt  arguments gt           lt  buildCommand gt       lt  buildSpec gt       lt natures gt           lt nature gt org eclipse jdt core javanature lt  nature gt           lt nature gt org eclipse m2e core maven2Nature lt  nature gt       lt  natures gt   lt  projectDescription gt    and I had

User · Answer

Well  I tried everything posted here  unfortunately nothings works in my case  So  trying different combinations I came out with this one that solved my problem   1  Open the  classpath file at the root of your eclipse s project   2  Insert the following entry to the file    lt classpathentry kind  con  path  org eclipse m2e MAVEN2 CLASSPATH CONTAINER  gt           lt attributes gt               lt attribute name  maven pomderived  value  true   gt               lt attribute name  org eclipse jst component nondependency  value     gt           lt  attributes gt   lt  classpathentry gt     Then  rebuild your project at eclipse  Project- Clean-Build   You now can check at the Java Build Path of you project at the Libraries tab the Maven Dependencies included

User · Answer

This same problem happened to me  and it was because there an error in downloading a jar due to repo issues  indicated by a red flag in the pom xml    I added another repository so the red flag in the pom xml disappeared and Eclipse then loaded the pom again  resolved its issue and listed the maven dependencies in Project Explorer  it sounds simple and obvious to resolve visible issues  but since Eclipse was quite happy to run maven  and build successfully  it was not obvious that the red flag and repo issue were at the root of its unwillingness to parse the pom and list the maven dependencies

User · Answer

I changed my project facet to java and copy pasted a working maven projects  classpath content to this project  This resolved my issue

User · Answer

Problem solved   I don t know what exactly solved it  but I did 4 things in Eclipse    Window- Preferences  Maven- Installations  Global settings -  open file and hardcoded localRepository Project- Clean right click on project  Maven- Update dependencies right click on project  Maven- Update project configuration   I guess it was the Update dependencies since right after first two there were no change

User · Answer

for me issue was due to multi module project     delete project from disk checkout project from your repo and import as maven project in eclipse clean install

User · Answer

I was also facing the same issue  it got resolved by using below   right click on Project- gt  maven- gt Update Project- gt Force update

User · Answer

My issue sounds similar so I ll add to the discussion  I had cancelled the import of an existing maven project into Eclipse which resulted in it not being allowed to Update and wouldn t properly finish the Work Space building   What I had to do to resolve it was select Run As    - gt  Maven build    and under Goals I entered dependency go-offline and ran that   Then I right clicked the project and selected Maven - gt  Update Project    and updated that specific project    This finally allowed it to create the source folders and finish the import

User · Answer

It s so amazing that this one problem has so many different causes and possible solutions   I found yet a different solution that worked for me   Well  it s not so much a solution but a discovery  I can see the Maven Dependencies node in the Package Explorer  which is the default for the Java perspective  but I can not see it in the Java EE perspective  which uses the Project Explorer by default   Both of those explorers look very similar at quick glance  so you may expect to see the Maven Dependencies in both   As I was trying to figure this out  I hadn t realized that difference  so it wasn t really a problem for me in the end after all

User · Answer

Here is the steps which i followed    1  Deleted maven project from eclipse   2  Deleted all the file  setting  classpath target  other than src and pom from my source folder   3  imported again as a maven project  4  build it again  you should be able to see maven dependencies

User · Answer

Th ROOT CAUSE of this issue is that  when you port a project to a new machine  you have to delete the   project  file in the root of your project  and try to import that  This makes the import smooth and Maven dependencies are properly configured for me  Note  You should exclude  project from Git versioning

User · Answer

Just in case anybody has tried all the other options and you are still stuck  try right-clicking on the project folder  head over to Maven option and click the  add dependency  button  For some reason Eclipse isn t updating the dependencies manually from the pom xml at first try

User · Answer

Maven Dependencies  What solved it for me in Eclipse  I added the dependency in the  pom  file  I did a build  but could not see the Maven Dependency in the Eclipse  Next Step  Closed the project  Then Reopened the project  I could see the Maven dependencies

User · Answer

window -  preferences -  Maven -  Instalations -  Global Settings  C  Program Files  x86  apache-maven- version  conf settings xml  mvn dependency tree mvn dependency resolve  once it points to the correct settings file  right click on project    update dependencies  update project configuration  once it is not loaded or code still keep n errors  close   open project

User · Answer

All above did not worked with me  For the fix was only to delete the repository folder under  m2 and then do a maven update from eclipse

User · Answer

From my end  I have tried all these and none of them worked  The most probable problem with this is that you have added more than one dependency  hence it is mandatory to wrap them in a  lt dependencies gt   lt  dependencies gt  tag  Hope it helps

User · Answer

I had a similar problem   I solved it by running the Maven- Update Project Configuration action

User · Answer

If you have  nested paths  errors after performing Maven -  Update Project Configuration  or in Juno it s  Update Configuration      then your build path is misconfigured   Right-click project -  Build Path -  Configure Build Path  Ensure that only   src  and directories at that level are included  If you have e g    src  and also   src main resources  present  this is incorrect  The second resource    src main resources   is  nested  under the first    src   which is causing your inability to import resources  since it prevents eclipse from seeing maven dependencies

User · Answer

Below solution worked for me -  1- Go to project directory  2- run mvn eclipse eclipse  Hope mvn is added in your path   3- run mvn clean install  Refresh your project in Eclipse and check

User · Answer

I experienced a similar problem lately after i created a maven project  the maven dependencies folder did not appear in the project structure To solve this simply add any dependency in the pom file  such as in code below  or right-click on the project and go to maven and select add dependency  search for any dependency such as junit add this  and the maven dependency should appear on your project structure now    lt dependencies gt    lt dependency gt    lt groupId gt org springframework lt  groupId gt    lt artifactId gt spring-context lt  artifactId gt    lt version gt 4 2 9 RELEASE lt  version gt    lt scope gt runtime lt  scope gt    lt  dependency gt   lt  dependencies gt

User · Answer

Well  I tried everything posted here  unfortunately nothings works in my case  So  trying different combinations I came out with this one that solved my problem   1  Open the  classpath file at the root of your eclipse s project   2  Insert the following entry to the file    lt classpathentry kind  con  path  org eclipse m2e MAVEN2 CLASSPATH CONTAINER  gt           lt attributes gt               lt attribute name  maven pomderived  value  true   gt               lt attribute name  org eclipse jst component nondependency  value     gt           lt  attributes gt   lt  classpathentry gt     Then  rebuild your project at eclipse  Project- Clean-Build

User · Answer

For the following steps worked in my case   1 On eclipse  right click on the desired project Maven -  Disable Maven Nature  2 Right click again then go to Properties  Delete every evidence of external Maven dependency leaving only JRE System Library   3 Right click one more time on the project then go to Configure -  Convert to Maven Project  it worked for me also

User · Answer

mvn eclipse clean   then from eclipse   Maven Update Project  does the trick

User · Answer

For me the problem was maven couldn t find the settings xml file which is located in myMavenFolder conf   What I did to fix the issue was to select the right location of the settings xml file from eclipse  Window -  Preferences -  Maven -  User Settings  Finally  hit apply and update your project

[eclipse] Missing Maven dependencies in Eclipse project

Examples related to eclipse

Examples related to maven-2

Examples related to m2eclipse