score:152

Accepted answer

i had to do it slightly different to work for me:

  1. rightclick project, remove maven nature (or in newer eclipse, "maven->disable maven nature")
  2. mvn eclipse:clean (with project open in eclipse/sts)
  3. delete the project in eclipse (but do not delete the sources)
  4. import existing maven project

score:0

it helped in my case

rightclick project, remove maven nature mvn eclipse:clean (with project open in eclipse/sts) delete the project in eclipse (but do not delete the sources) import existing maven project

score:0

my tricky solution is:

  1. open your windows task manager,
  2. find the javaw.exe process and highlight it, then end it by end process
  3. in eclipse project browser, right click it and use maven -> update project again.

issue is resolved.

if you have tomcat server running in eclipse, you need to refresh project before restart tomcat server.

score:1

i removed my .classpath file in my project directory to correct this issue. no need to remove the maven nature from the project in eclipse.

the specific error i was getting was: project 'my-project-name' is missing required java project: 'org.some.package-9.3.0 but my project wasn't dependent on org.some.package in any way.

perhaps an old version of the project relied on it and maven wasn't properly updating the .classpath file.

score:2

slightly different option usually works for me:

  1. "mvn eclipse:eclipse" for this project in the command line.
  2. "refresh/f5" this project in eclipse.

that's all, no need to re-import but need to have the terminal window handy.

score:2

i solved this by looking at this comment on jbide-11655 : deleting all .project, .settings and .classpath in my projects folder.

score:2

i imported the project as general project from git repository.

  • deleted .settings, .project and .classpath in project's folder
  • configure -> convert to maven project. only this solved the problem in my case.

score:2

i have that problem and my solution is going source folder and run command line: mvn clean install -dskiptests eclipse:eclipse then return eclipse workspace and refresh project. hope that help!

score:2

your command line mvn eclipse project generator may not be the same version as that of your eclipse, and eclipse doesn't understand for your command line tool is generating. just use eclipse's in this case:

  • remove the project from eclipse (including all modules if multi-module)
  • run: rm -rf .settings/ .project .classpath to delete eclipse project files, also from modules
  • import your project as an existing maven project

score:3

this issue (https://bugs.eclipse.org/394042) is fixed in m2e 1.5.0 which is available for eclipse kepler and luna from this p2 repo :

http://download.eclipse.org/technology/m2e/releases/1.5

if you also use m2e-wtp, you'll need to install m2e-wtp 1.1.0 as well :

http://download.eclipse.org/m2e-wtp/releases/luna/1.1

score:4

after trying all these procedures it still didn't work for me. what did work was

  1. go into file explorer and delete the .classpath file under the project's root folder
  2. run maven update within eclipse, and check force update of snapshots/releases

our current work required integrating a number of disparate projects so unfortunately use of snapshots in a production environment were required (taboo in maven circles)!

score:9

this is all you need:

  1. right-click on your project, select maven -> remove maven nature.

  2. open you terminal, navgate to your project folder and run mvn eclipse:clean

  3. right click on your project and select configure -> convert into maven project

  4. right click on your project and select maven -> update project

score:86

  • i just went to properties -> java build path -> libraries and removed the blue entries starting with m2_repo.

  • after that, i could use maven -> update project again


Related Query

More Query from same tag