eclipse project not importing the jar packages in local Maven repository

I am开发者_运维问答 facing a problem in setting my eclipse project. The problem is whenever I am creating a new project and import the code.Eclipse is not resolving the packages which are present in the jar files which are present in the C;/..../user/.m2/repository.

Hence it's giving a lot of compilation errors until I add all the required jar files manually in the build-path by going to "Add External Jars"

I saw that M2_REPO is present in my Eclipse classpath.But still it is not resolving the packages. Please suggest how this problem can be resolved.

Gaurav

---

I've been having a similar error in Eclipse on OSX. In Eclipse on the Mac, there is no "Maven" entry when you right-click on a project in the explorer.

However!

I just discovered that if I right click and then click "Validate", it suddenly magically resolves all the dependencies. No idea why, but maybe this will help.

---

I've had this issue on Eclipse Kepler EE which comes prebuilt with m2e, I finally got it working by doing the following on each project:

• Right click on the Project
• Select Properties
• Select Maven
• Uncheck the option that says: Resolve Dependencies from Workspace projects

It should pop up with a box that says Maven setting has changed. Do you want to update project configuration. Click Yes to this.

To confirm:

• Right click on the project
• Select Properties
• Select Java Build Path
• Check the Libraries tab under Maven dependencies that all the jar you expected are now there.

---

close your project, and remove your project settings files: .project, .classpath, .settings/. Then re-import this project. It will be ok.

---

Though this answer is late. But it can help the future audience.

You can give it a try using Project(Right-Click) -> Maven -> Update Project. To select all or the number of projects you want to update.

This worked for me.

---

Have you put all needed dependencies in the pom.xml? Even if the Jars are already in your local repository, each project needs its dependencies mentioned in the pom.xml to resolve the dependencies. If you do that, m2eclipse will automatically resolve the build path.

---

Another possibility. Are you running Eclipse using JDK or JRE - the default is JRE. You will see a warning in Eclipse console, if so.

maven eclipse plugin will not work correctly unless run with JDK.

---

I just had a similar problem. The JDK was there, the problems view was set to Show All, and yet there were hundreds of unresolved type errors. Not even Refresh (F5) would work.

In the Project|Properties|Java Build Path|Libraries window I was seeing only the JRE System Library, but not the desired "Maven Dependencies" entry. And "Maven Dependencies" was also missing from the Package Explorer view as well.

I finally fixed this by right clicking on the project in the Package Explorer, selecting Maven from the menu, then selecting "Update Project Configuration." This added "Maven Dependencies" and all the errors went away.

This was nice because prior to this fix I had to treat Eclipse like a dumb editor and run mvn compile on the commandline to find errors.