The following refactoring actions are broken if a class uses a lombok annotation: 
* rename of a class
* rename of a variable
* change of method parameters

I didn't tried the remainder of the refactorings. 


Tested with: 
* Netbeans 8.0 RC1
* Lombok 1.12.4

Steps to reproduce: 
* File =>New Project => Maven => new Java Application
* Modify Pom with the following dependency

<dependency>
  <groupId>org.projectlombok</groupId>
  <artifactId>lombok</artifactId>
  <version>1.12.4</version>
</dependency>

* Create a Pojo, use for example the @Data Annotation (applies for all lombok annotations so far)
* hit refactoring

Usually it doubles the class and sometimes the refactored and unrefactored parts of the class are tangled and messed up. 

a related Bug report in lombok can be found at https://code.google.com/p/projectlombok/issues/detail?id=106