On 08/09/2012, at 12:53 PM, Russel Winder wrote: > On Wed, 2012-09-05 at 10:18 +0100, Luke Daley wrote: >> >> >> >> On 05/09/2012, at 9:13 AM, Russel Winder <[email protected]> wrote: >> >>> I am finding that Gradle builds fine with the Oracle Java 8 release, but >>> that it fails with the Project Lambda build. Is this a "Don't Care" type >>> issue or something worth following up? >> >> It won't be a priority, but if it's quick and not risky to fix then we'd fix >> it. >> >> How does it fail? > > As per below. I was going to start an issue for this, but I couldn't > find a link to an issue tracker on the Gradle front page. > > > :native:classpathManifest > :native:compileJava > /home/Checkouts/Git/Git/Gradle/subprojects/native/src/main/java/org/gradle/internal/nativeplatform/jna/Kernel32.java:23: > error: cannot find symbol > import com.sun.jna.win32.W32APIOptions; > ^ > symbol: class W32APIOptions > location: package com.sun.jna.win32 > /home/Checkouts/Git/Git/Gradle/subprojects/native/src/main/java/org/gradle/internal/nativeplatform/jna/Kernel32.java:32: > error: cannot find symbol > Kernel32 INSTANCE = (Kernel32) Native.loadLibrary("kernel32", > Kernel32.class, W32APIOptions.UNICODE_OPTIONS); > > ^ > symbol: variable W32APIOptions > location: interface Kernel32 > 2 errors > :native:compileJava FAILED > > FAILURE: Build failed with an exception.
I couldn't find anything saying that the Project Lambda JDK doesn't contain the JNA bridge, but that's surely what it looks like. I'm inclined to say we don't care about this. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
