I add guava 17.0 to my pom.xml, Eclipse automatically rebuilds project.
Ran mvn dependency:resolve
, maven shows com.google.guava:guava:jar:17.0:compile
in the list of resolved files.
However when in Eclipse I try to auto-complete com.google.g
, it says "No default proposals". I've added dependencies in my pom.xml before, run mvn dependency:resolve
and Eclipse picked them up immediately. What's different this time?
I've tried the following so far:
mvn clean
followed by mvn install
I can see target/<projname>-1.0-SNAPSHOT/WEB-INF/lib/guava-17.0.jar
.
My configuration:
The suggestion by @khmarbaise works best and solves all problems.
Just delete the project from Eclipse.
Re-import as "Existing Maven Projects" and point it towards the directory that contains the project's pom.xml
file.
Let Eclipse's m2e
plugin handle the rest
Worked flawlessly for me.
The following advice (taken from https://developers.google.com/appengine/docs/java/webtoolsplatform#maven) may only apply to GAE projects, but seems like it should be generally applicable (my project is GAE, so can't be sure):
The directory at the root of the Maven project must not contain any of the following:
1. A subdirectory named target 2. A subdirectory named .settings 3. A file named .classpath 4. A file named .project