ourferro.blogg.se

• #ECLIPSE JUNO DOWNLOAD FOR WINDOWS 7 KEYGEN#

#ECLIPSE JUNO DOWNLOAD FOR WINDOWS 7 KEYGEN#

This has nothing whatsoever to do with us rewriting your class file post compilation, instead, something in lombok is putting the ecj AST into an invalid state, and sometimes this leads to invalid class files instead of the more usual exceptions during compilation.Even though we only change a tiny bit, it is possible the operation of running the whole thing through ASM just breaks things in this specific case due to a bug in ASM. We have to read in your method, change it, and write it back out, at the class file level.

This should be easy to figure out, and easy to solve. Our rewrite-classfile-as-it-is-written-to-disk mechanism which actually removes the call to Lombok.sneakyThrow entirely is causing this issue.I am going to mark it as accepted though, because while I haven't personally verified it (that would involve downloading a bunch of tools), the bug reporter has obviously put in all due care. I'm going to push v0.11.8 out with this bug open. The problem seems to relate be the inter-play between the Eclipse Java 7 compiler and Lombok.Įrr, that's actually probably relatively time-consuming to solve. The test passes when using Eclipse Java 6 compiler and running the test in Eclipse using Oracle JDK The test passes when compiling and running from the Maven command line (both Oracle JDK6 & Oracle JDK7). Please provide any additional information below. I have also tried edge build 0.11.7 01:46 UTC with same result. What version of the product are you using? On what operating system? : Bad type on operand stack in method Foo.applyTo(ZLFoo )V at offset 25 Instead the test fails with the following report. What is the expected output? What do you see instead? Use Eclipse JUnit runner to run the Junit Test 'FooTest'.Import the Maven project to Eclipse Juno.