Lombok with Eclipse Mars M6

[Jason van Zyl]

Hi,

Has anyone happened to have tried Lombok with Eclipse Mars M6? It's not working for me locally but I construct my own Eclipse distro from the Eclipse p2 repos so I'm wondering if it's just something I've done or a general issue with Mars interacting with Lombok. I want my Lombok back! :-(

Jason

[Jason van Zyl]

Just a note that I found the reported issue where the full path to the lombok.jar might be required for customized distributions and this is not working in my case. Also note I've used lombok with a custom built distribution and all was working well until I switched over to Eclipse Mars. I'll try to debug and see what's going on.

[Roel Spilker]

I just installed Mars M6 and also get an error in workspace/.metadata/.log (see below).

Do you get something similar?

!ENTRY org.eclipse.e4.ui.workbench.swt 4 2 2015-03-31 00:35:02.949

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.e4.ui.workbench.swt".

!STACK 0

java.lang.VerifyError: Bad type on operand stack

Exception Details:

  Location:

    org/eclipse/jdt/internal/compiler/ast/MessageSend.resolveType(Lorg/eclipse/jdt/internal/compiler/lookup/BlockScope;)Lorg/eclipse/jdt/internal/compiler/lookup/TypeBinding; @630: putfield

  Reason:

    Type 'java/lang/Object' (current frame, stack[1]) is not assignable to 'org/eclipse/jdt/internal/compiler/lookup/MethodBinding'

  Current Frame:

    bci: @630

    flags: { }

    locals: { 'org/eclipse/jdt/internal/compiler/ast/MessageSend', 'org/eclipse/jdt/internal/compiler/lookup/BlockScope', long, long_2nd, integer, integer, '[Lorg/eclipse/jdt/internal/compiler/lookup/TypeBinding;', 'java/lang/Object' }

    stack: { 'org/eclipse/jdt/internal/compiler/ast/MessageSend', 'java/lang/Object' }

  Bytecode:

.....

.....

    same_frame(@1980)

    same_frame(@2022)

    same_frame(@2045)

    same_locals_1_stack_item_frame(@2046,Object[#296])

at org.eclipse.jdt.internal.compiler.parser.Parser.newMessageSend(Parser.java:10886)

at org.eclipse.jdt.internal.compiler.parser.Parser.consumeMethodInvocationName(Parser.java:5325)

at org.eclipse.jdt.internal.compiler.SourceElementParser.consumeMethodInvocationName(SourceElementParser.java:445)

at org.eclipse.jdt.internal.compiler.parser.Parser.consumeRule(Parser.java:7022)

at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:11112)

at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:11360)

at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:11317)

at org.eclipse.jdt.internal.compiler.SourceElementParser.parseCompilationUnit(SourceElementParser.

--
You received this message because you are subscribed to the Google Groups "Project Lombok" group.
To unsubscribe from this group and stop receiving emails from it, send an email to project-lombo...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jason van Zyl]

Hi,

I have something similar. For my particular project I get the following:

https://gist.github.com/jvanzyl/ab9bb775c3d176cd0b07

The specific codebase I imported into Mars M6 is the following:

https://github.com/cobbzilla/s3s3mirror/tree/2.0-stable

Happy to provide any other details you need.

On Monday, March 30, 2015 at 3:45:09 PM UTC-4, Jason van Zyl wrote:

[Reinier Zwitserloot]

Roel and I did some testing and it's not you, it's mars in general. The good news is: We think we have a handle on how to fix it.

See https://code.google.com/p/projectlombok/issues/detail?id=802

for more detail, and you can track that issue for updates.

Thanks for letting us know about the problem!

 --Reinier Zwitserloot

--

[Jason van Zyl]

Thank you for looking into it! Much appreciated! 

On Monday, March 30, 2015 at 3:45:09 PM UTC-4, Jason van Zyl wrote:

[Roel Spilker]

I did find a workaround. I got it working by running Eclipse on java7 and adding "-XX:-UseSplitVerifier" to the vmargs in eclipse.ini

This instructs the class verifier to use the pre-java6 verifier. However, when I used java8u31, this didn't work. As far as I can see, this option is no longer supported. Some people suggest using -noverify, this also didn't seem to work.

Roel

[Jason van Zyl]

Great, thanks. I'll give it a try.

On Monday, March 30, 2015 at 3:45:09 PM UTC-4, Jason van Zyl wrote:

[Jason van Zyl]

I tried this option and progressively raised the -XX:MaxPermSize option to 512m and still keep getting java.lang.OutOfMemoryError: PermGen space with any project that uses Lombok.

On Monday, March 30, 2015 at 3:45:09 PM UTC-4, Jason van Zyl wrote: