Retrolambda in library projects and main projects can break the build

I actually think this is related to #60.

Project setup:

• library using retro lambda
• […]
• main-project using retro lambda

Now from a gradle clean one always needs to build twice.

The first build will fail on main-project:compileRetrolambdaDebug

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':main-project:compileRetrolambdaDebug'.
> Process 'command 'C:\Program Files\Java\jdk1.8.0_40\bin\java.exe'' finished with non-zero exit value 1

The second build succeeds. I think it’s because the repackaged files are not used the first build, but they are the second time (when it’s cached due to incremental).

[zeshaoaaa]

@wheelerruss

retrolambda { jvmArgs ‘-noverify’ }

I added. but the error stil existing.

:app:compileRetrolambdaDebug Error:Could not create the Java Virtual Machine. Error:A fatal exception has occurred. Program will exit. Unrecognized option: -arg1 Error:Execution failed for task ‘:app:compileRetrolambdaDebug’.

Process ‘command ‘F:\DDH\java\jdk\bin\java.exe’’ finished with non-zero exit value 1

[wheelerruss]

@evant that worked for me, thanks a lot

i.e. adding

retrolambda { jvmArgs ‘-noverify’ }