jdk8 about gwt-maven-plugin

[tbroyer]

The plugin doesn't read the configuration from maven-compiler-plugin, but both can be configured using the same maven.compiler.source property.

I.e. you either need:

<plugin>
  <artifactId>maven-compiler-plugin</artifactId>
  <configuration>
    <source>7</source>
  </configuration>
</plugin>
<plugin>
  <groupId>net.ltgt.gwt.maven</groupId>
  <artifactId>gwt-maven-plugin</artifactId>
  <configuration>
    <sourceLevel>7</sourceLevel>
  </configuration>
</plugin>

or

<properties>
  <maven.compiler.source>7</maven.compiler.source>
</properties>

[h0ru5]

Confirmed working!

whenever compiler-plugin has classes to compile.
However, it fails when maven-compiler-plugin has nothing to do:

[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ inherit ---
[INFO] Nothing to compile - all classes are up to date

...

[INFO] --- gwt-maven-plugin:1.0-alpha-3:compile (default) @ inherit ---
[INFO] Unexpected internal compiler error

....

Caused by: java.lang.IllegalArgumentException: Unknown sourceLevel value: 1.8

Or is it my local setup?

[tbroyer]

How's your local setup? Did you use one of the alternatives I gave above? Or something else?

[h0ru5]

Its just maven 2 on jdk8
I used the second alternative you mentioned (maven.compiler.source).

see here: https://github.com/h0ru5/gwt-chromeapp

It does work when I run a mvn clean before it, or when there are changes that force maven-compiler-plugin to recompile.
But it's really not showbreaker

I might dive deeper into it next week

[h0ru5]

sorry, my fault. the config of maven-compile-plugin was still there. that causes this strange behaviour

[tbroyer]

It might be due to Maven 2. Maven 2 is dead and buried, you should use 3.0 or 3.1 by now. I'll try it with Maven 3 if I remember, and find time, etc. ;-)