This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 256888 - Lombok annotated project become broken with last build
Summary: Lombok annotated project become broken with last build
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 8.2
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-01 10:37 UTC by Maksim Khramov
Modified: 2016-06-15 08:35 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maksim Khramov 2015-12-01 10:37:19 UTC 
Product Version: NetBeans IDE Dev (Build 201511301649)
Java: 1.8.0; Java HotSpot(TM) 64-Bit Server VM 25.0-b70

I have a java web project using Lombok annotations processor. With last build (201511301649) the project code marks as broken: lombok logger field marks as missed. Lombok generated getters and setters are marked as missed too.
(Build at 26'th of November was works ok)

Also I see exceptions in IDE Log:
INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation processing error:
java.lang.NoSuchFieldError: pid
	at lombok.javac.JavacAST.packageDeclaration(JavacAST.java:107)
	at lombok.javac.JavacAST.<init>(JavacAST.java:81)
	at lombok.javac.JavacTransformer.transform(JavacTransformer.java:67)
	at lombok.javac.apt.Processor.process(Processor.java:250)
	at lombok.core.AnnotationProcessor$JavacDescriptor.process(AnnotationProcessor.java:115)
	at lombok.core.AnnotationProcessor.process(AnnotationProcessor.java:165)
	at lombok.launch.AnnotationProcessorHider$AnnotationProcessor.process(AnnotationProcessor.java:58)
[catch] at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:856)
Comment 1 Tomas Zezula 2015-12-02 17:39:24 UTC 
It's a Lombok bug caused by a usage of internal javac (non api) classes in the Lombok.
I will create a patch for Lombok and submit a bug request on Lombok.
Comment 2 Maksim Khramov 2016-01-10 12:26:31 UTC 
Filed issue at lombok project: https://github.com/rzwitserloot/lombok/issues/997
Comment 3 Tomas Zezula 2016-06-15 08:35:09 UTC 
Fixed by Lombok team https://github.com/rzwitserloot/lombok/issues/997#issuecomment-174016952.
Thanks!