Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) java java

Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile)


Deleting full .m2/repository local repository solved my problem.

Or else you need to know what plugins are you using exactly with their dependencies as one of the plugin suffered a problem while downloading.


Deleting full .m2 local repository solved my problem, too.

If you don't know where it is, the locations are:

Unix/Mac OS X – ~/.m2/repositoryWindows – C:\Documents and Settings\{your-username}\.m2\repository         ( %USERPROFILE%\.m2\repository too, as suggested by **MC Empero** )


I am adding more points to the solution by @Rushi Shah

mvn clean install -X helps to identify the root cause.

Some of the important phases of Maven build lifecycle are:

clean – the project is clean of all artifacts that came from previous compilationscompile – the project is compiled into /target directory of project rootinstall – packaged archive is copied into local maven repository (could in your user's home directory under /.m2)test – unit tests are runpackage – compiled sources are packaged into archive (JAR by default)

The 1.6 under tag refers to JDK version.We need to ensure that proper jdk version in our dev environment or change the value to 1.7 or 1.5 or whatever if the application can be supported in that JDK version.

<build>    <plugins>        <plugin>            <groupId>org.apache.maven.plugins</groupId>            <artifactId>maven-compiler-plugin</artifactId>            <version>3.0</version>            <configuration>                <source>1.6</source>                <target>1.6</target>            </configuration>        </plugin>    </plugins></build>

We can find the complete details on Maven build lifecycle in Maven site.