More specifically: A call to a static or regular method of an annotation-processor-created class is shown with an error "cannot find symbol" yet the modules that call it build just fine, and work properly at run-time.

Now after some rebuilding, closing and reopening Netbeans and some more cleaning & rebuilding the error has gone away.  Most odd - this same cleaning and rebuilding went on before yet the error persisted.

At some stage something really broke and even the import statement of the generated class failed.  I checked the produced JAR file and the class was there as intended.  I cleaned and rebuilt all projects, restarted and cleaned several times and nothing changed.

Eventually I closed Netbeans, deleted the folder "8.0" in %USERPROFILE%\AppData\Local\NetBeans\Cache\ and now everything is working again, so I would say there is definitely a bug off sorts involved - something is not getting refreshed.

I am experiencing (roughly) the same problem.  I reproduced the problem in Netbeans 8.0.2 in Ubuntu 14.04 with Oracle JDK 7.

In a @PostConstruct method, I'm trying to call a method on an @Inject object.  Odd thing is that it recognizes (autocompletes) all of the methods on that object except for one.  That one object has the same footprint as all the others (i.e. "public void").  I have that object's .java file open in NB and while NB doesn't recognize the method, it all compiles just fine.

What would be needed to demonstrate this case?

Additionally, while it flags the method-call with "Cannot find symbol", the line with the red exclamation point and light bulb, AND the file in the Projects window, it does not flag the filename at the top as having an error.

Created attachment 152041 [details]
Example of the cannot find symbol.

When I get the 'cannot find symbol', along with the problems listed in the comments above, I also experience the impossibility to run tests involving flagged code, because I get ExceptionInInitializerError. Rebuilding solves issues, but of course it's time consuming when testing. 

Cleaning Netbeans cache fixes the problem, but (on windows, at least) takes time 
and seems to be required often.

Tested with Netbeans 8.0.2, Maven 3.0.5, JDK 1.7_10, Windows 7

In my case the import statement for the generated class was underlined, even after stopping NetBeans, deleting the cache, restarting NetBeans and rebuilding everything. This problem vanished after I installed the latest plugin updates today. I suggest to install the latest updates and maybe close this bug.

Disregard my last comment, the "problem gone" state was very temporary.

My case:
Two Maven projects M (model) and S (service). S uses M as a dependency.
M has generated classes.

In project S, a generated class from M does not show up in suggestions for import statements. When manually adding the correct import statement, the name of the generated class is underlined and the class using it is marked as erroneous in the file tree and in "Action Items". "Go to source" using Ctrl+Click on the name of the generated class does not work.

Tested with nightly build 201609130002. Deleting the cache (while NetBeans is closed) does not help.