For me the cause seems to be a downgrade from maven 3 to maven 2.
The maven metadata xml in the local repository, installed by maven 3, contained something (extension) that was incompatible with maven 2.
Since 0.3, Jongo uses Mongo Java driver at a deeper level to enhance performance.
Instead of converting results into strings and unmarshalling strings into objects, it works at level (query marhalling works the same since 1.0).
Default Execute(Default Maven.java:247) at org.apache.maven. Default Maven.execute(Default Maven.java:104) at org.apache. Maven Cli.execute(Maven Cli.java:427) at org.apache. Delegating Method Accessor Impl.invoke(Unknown Source) at reflect.
Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher. Launcher.launch Enhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher. Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher. With Exit Code(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher. Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin. Compilation Failure Exception: Compilation failure Unable to locate the Javac Compiler in: C:\Program Files\Java\jre6\..\lib\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. Abstract Compiler Mojo.execute(Abstract Compiler Mojo.java:516) at org.apache.maven.plugin.
Update Maven project each time after including new dependencies. After creating class call the static run method of Spring Application class.
Like a file path of the file containing the problem, for example :) In my case, the issue was due the extra spaces.
To fix this error, i removed the spaces before the tag on the line where the error has occurred.
R35x_v20090715file.encoding=Cp1252 file.encoding.pkg=file.separator=\ graphicsenv= java.specification.version=1.6 java.vendor=Sun Microsystems Inc. java.vendor.url= java.bug= info=mixed mode name=Java Hot Spot(TM) Client VM specification.name=Java Virtual Machine Specification specification.vendor=Sun Microsystems Inc. Also, the default runtime in Eclipse (found in the "Installed Runtimes" page of the Preferences dialog) might be a JRE.
specification.version=1.0 vendor=Sun Microsystems Inc. I've noticed that this sometimes occurs due to multiple VM configurations being obtained, with the first or the last being applied.
Search for updating maven:
In the following code, we are calling run method and passing class name as argument.