Eclipse updating maven dependencies waiting
6/25/07 PM CDT: ERROR mojo-execute : compiler:compile : Compilation failure Unable to locate the Javac Compiler in: C: Program Files Javaj2re1.4.2_14..Please ensure you are using JDK 1.4 or above and not a JRE (the tools.javac. In most cases you can change the location of your Java installation by setting the JAVA_HOME environment variable.
The Maven project checkout is based on generic Maven SCM API (which supports number of SCM providers out of the box) and we don’t have any information about Maven projects before the actual checkout (e.g.By default Eclipse registers JRE it is started in, but this can be configured on “Window / Preferences / Java / Installed JREs” preference page. Such errors indicate use of non-API classes and those access rules are defined by Eclipse JDT.You can change compiler settings to not fail on those restrictions in workspace settings in Window / Preferences / Java / Compiler / Errors/Warnings / Deprecated and restricted API / Forbidden reference (access rules) / Warnings; or per-project from Project / Properties / Java Compiler / Errors/Warnings / Deprecated and restricted API / Forbidden reference (access rules) / Warnings M2Eclipse is using Maven .We hope that such regressions and incompatibilities will be fixed in the future releases of Maven 3.0.Note that m2eclipse is always using embedded Maven runtime when running Maven builder, importing projects and updating project configuration, however you can configure m2eclipse to use external Maven installation when launching Maven using “Run as¦ / Maven XXX” actions.
This can be changed in the Maven settings in “Window / Preferences / Maven / Goals to run on project import” (e.g.