Today I downloaded Gradle 2.5 and did a full build on our project. What is really surprising to me is a build failure due to a compile error - which is not produced using Gradle 2.4!
This is the output:
:de.uvdms.ui.main:compileJava
Q:\sources\trunk_clf\uvdms\de.uvdms.ui.main\src\main\java\de\uvdms\ui\core\jetty\webapp\FavWSSpringS
ervlet.java:36: error: try-with-resources not applicable to variable type
try (ClassPathXmlApplicationContext ctx = new ClassPathXmlApplicationContext(getInitParameter(
“contextfile”))) {
^
required: AutoCloseable
found: ClassPathXmlApplicationContext
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
:de.uvdms.ui.main:compileJava FAILED
Please note, Gradle settings and compile settings did not change. The only thing I’m changing in my environment is the path to GRADLE_HOME.
GRADLE_HOME=D:\Java\gradle-2.5
GRADLE_OPTS=-Dorg.gradle.daemon=true -Dorg.gradle.java.home=D:\java\jdk1.7 -Dorg.gradle.deprecation.
trace=true
GRADLE_USER_HOME=Q:\gradleCache
I understand this is an error produced by compiler. But somehow this must be triggered by Gradle, because using the same compiler and Gradle 2.4 does not produce a compile error.
What version of the Spring Framework are you trying to depend on and what version is ending up in your compile classpath? ClassPathXmlApplicationContext did not implement AutoCloseable until Spring 3.2.0.RELEASE, which is required for the try-with-resources syntax as mentioned in the compile error.
Check that the spring-context dependency on your compile classpath is >= 3.2.0.RELEASE and if you see a difference between the version resolved with Gradle 2.4 and Gradle 2.5. Ordering might also be important if there’s some way that you have more than one version on the compile classpath.
I hit a similar issue but the dependency output is the same (2.4 vs 2.5). I wonder if the default JavaCompile options have changed?
Update: using the -d option and can see the ordering of the classpath is completely different between versions. This must have exposed a class conflict I was not aware of.
Somehow, this whole thing stays mysterious. Because of some other dependency conditions (JAX WS), I’ve found, that I cannot use " a newer version (1.9) of jaxws-spring", but had to stay with this version 1.8, which I thought was the culprit of my compile problem with Gradle 2.5.
Now, the compile works with jax-ws-spring-1.8. Don’t know why.
I resolved the “mystery” by explicitely including our Spring-version in the dependency graph; somehow this is forcing the version and therefore overriding the dependencies jaxws-spring declares.