Updating maven dependencies refreshing maven model dating site in hong kong
In my case it seems to be caused by a bad jar file combined with the zip libs not throwing a proper exception, just a Null Pointer Exception. Version: Neon.3 Release (4.6.3) Build id: 20170314-1500 The fix/trick for me was deleting my local repository in ~/.m2/repository in order to remove local dependencies and rebuilding my project in which fresh dependencies are pulled down. This might also arise due to the presence of circular dependency in your eclipse workspace.
I'm using STS and the only thing that worked was to go into my STS directory and add a "-clean" to the top of the file.
That should result in better integration between Eclipse and maven, including automatically updating the Eclipse build path when the pom is changed.
As a quick check, after doing the import that way, you should see a group called Maven Dependencies in the Libraries tab of the project's Build Path (in Properties dialog).
You can then start up your workspace and run maven clean without errors.
(you can also remove the -clean tag from the ini file so it doesn't clean everytime you start it) Hope this helps someone.
As a last resort, you can delete your current Eclipse installation and install a new version.
I resolved the conflict, then tried a Maven update again and it worked. Null Pointer Exception at com.google.appengine.maven. Gae Runtime Gae Runtime(Gae Runtime Manager.java:85) at com.google.appengine.maven.
Gae Runtime Manager.ensure Gae Runtime With Sdk(Gae Runtime Manager.java:55) at com.google.appengine.maven.
Maven is a build and dependency management tool, not an IDE; expecting it to manage IDE-specific stuff is silly, in my opinion (I realize the Maven team thinks differently, that Maven should be responsible for managing your IDE, but that's nonsense).
So if you have the project available on your system, delete any Eclipse-specific files (typically just Existing Maven Projects to import the project.