I am using a different approach with maven, gwt and eclipse.

I am using the maven eclipse plugin to generate a .classpath and .project file and import the project manually into eclipse (not as a maven project).

My configuration for the maven eclipse plugin looks like this:







Hope that helps


This helped me:

  1. Delete the project from eclipse (but don't delete from disk)
  2. Close eclipse
  3. In your user folder there is .m folder.
  4. Delete repository folder underneath it (.m/repository).
  5. Open eclipse Import project as existing maven project (from disk).


If your pom is not specific as to the version of the maven-resources-plugin, that version will come from the superpom. By default, m2e uses an embedded copy of Maven 3.0.x. If the superpom there points to 2.4.3 and your 'outside-of-Eclipse' version asks for something else, then the Maven inside of Eclipse will go looking for 2.4.3 and fail due to the 'offline'.

Fix by configuring m2e to use the Maven installation you are using outside, or turning off 'offline' for one build.

If you want to use maven from your local installation instead of the embedded version that comes with m2e, You have to do this

Windows ==> Preferences ==> Maven ==> Installations ==> Click Add (select your local maven installation directory)

Installation Directory is not where local repository. It is where maven is installed.

After changing try right click on project then,

Maven ----> Update Project


Make sure you are not using the embedded Maven of Eclipse.

Go to Window->Preference ->Maven -> Installation->choose your own maven installation folder there.


If your company pays for IDE, you should ask for IntelliJ the IDE for Java, which I would say is better than Eclipse in many ways, not saying Eclipse is not good, that's just a good alternative. And you won't have this issue to start with

Related Query

More Query from same tag