He is running 1.7, since he gets an explicit message from the compiler
to use source "7" and he already posted the output of the mvn --version.
Have you tried the debug mode with -X to see what the maven compiler
does? Have you tried directly setting the properties to "1.7" in the
configuration instead of using properties (just for testing)? Also, you
could try dropping the configuration part (except the encoding) since
you are using the maven properties corresponding to that configuration.
Cheers,
Guillaume
Le 6/01/2012 09:52, Holger Hoffstaette a écrit :
On Fri, 06 Jan 2012 03:45:19 +0100, Johannes.Lichtenberger wrote:
On 01/06/2012 02:54 AM, Dave Wolf wrote:
Instead of "1.7" try simply "7".
Seems it doesn't have any impact. In Eclipse itself it doesn't seem to
change anything, too, but in Eclipse the build path is correct for all
projects. I just want to get `mvn` in the shell running after I've updated
the projects to Java 7 some time ago to double check if the unit tests are
working before commiting to the CI-Server (and to produce JARs).
I can compile JDK7 source just fine (using new 7-only classes etc., with
"1.7" as source/target:
..
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>${compiler.plugin.version}</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
..
maven-compiler-plugin is 2.3.2.
Try mvn --version to verify that you are really using the correct JDK.
-h
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
