In our project, we use javax.crypto, and under gradle-milestone-8 we get a compile error on class not found. Investigating this more, and starting off on a clean windows 7 box, I was able to figure out what went wrong.
Setup: * Fresh Windows 7 Professional * JDK 7.0r3 * gradle-milestone-8
The project has source and target 1.6.
When gradle tries to compile, it overrides the default bootclasspath. This new bootclasspath does not include jce.jar, which is where javax.crypto is stored. There might be other classes in the default bootclasspath that get omitted as well. If I change to project source and target to 1.7, it compiles fine. And gradle doesn’t set the bootclasspath on the ant javac task.
Using gradle-mileston-7, and source and target 1.6, the project compiles fine. However, javac prints a warning that bootclasspath is not set.
I have the same problem on linux when compiling using Java 7. If I set JAVA_HOME to point to jdk6, things compile fine.
Suggested fix: either bootclasspath is never unset unless explicitly defined in the gradle build file, or gradle is more intelligent about locating the correct jdk/jre for the target version, and figuring out the correct bootclasspath.