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.
Created attachment 123221 [details] Example project that demonstrates a non-visible public generated class. If use an annotation processor to generate a public class in module A, then module B with a dependency on module A cannot see that class, even though the generated class is public and in a module public package. See the attachment for an example project containing an annotation processor that generates a class in one module that is not visible from another module. See the README.txt for details.
Interesting case. I talk to the Java guys about this tomorrow.
So how interesting is it? :-) I'd like to be able to do this.
In fact it's not very interesting case. :-) The thing is that the project containing the AnnotationProcessor (AP) is not built when the projects are opened in the IDE and indexed. The JavaCustomIndexer cannot execute the AP as it does not exist. If you build the project containing the AP before you open the projects there are no errors. This behaviour is correct but the IDE should reindex (rescan) the source roots having the AP on the annotation processor path which currently does not happen which is a bug.
Fixed jet-main 2ecb86354a59. The APTUtils.verify now detects creation of an root containing the built AP and forces reindex of the affected source root. For NB 7.2 you can resolve the problem by coping the jar containing the AP and adding the copied jar to processor path rather than the project reference.
Sorry, I'll try to find more interesting problems. :-) "For NB 7.2 you can resolve the problem by coping the jar containing the AP and adding the copied jar to processor path rather than the project reference." I removed the Annotations module and put the annotation code in a separate Java project to create a JAR, then added the JAR in Libraries -> Wrapped Jars for the Services module. Since this is being done in a framework application, there is no "processor-path libraries" option, so I added "-processor ex.annotations.processors.MyServiceProcessor -processorpath /path/to/AP.jar" to the "Additional Compiler Options" field for the Services module. The ex.services.MyServiceName class is successfully generated as before, so the annotation processor is being found and is working. However the source in the Display module still can't see the generated ex.services.MyServiceNames, so the problem remains with your workaround, unless I'm misunderstanding. Can you please explain your workaround a little more. Thanks.
Fixed for NB 7.3: Please do not change the status for older releases it makes the issue tracking difficult for QE. For NB 7.2 : The first steps you have described sounds good to me, copy jar (it's important to have a copy outside the build), create a library wrapper for it and use it instead of the library. So far so good. Now comes the problem, the project is API Support project not regular Ant project and it does not have annotation processing path, right. You have added the AP to the additional compiler options, but these options are just the Ant options they are not used by the editor or compile on save. These features don't know about them, so the IDE in fact does not run the AP only the Ant runs it when it's built. Fortunately when the processor path is not given javac uses classpath to resolve APs (adding the library wrapper module to classpath instread of the Annotations project is enough). Just removing the additional compiler options should fix the problem. As single example is better than tons of comments I am attaching your Annotations Suite which is changed to use library module wrapper. I've tried it in NB 7.2 and it works fine for me, the actions correctly see the generated MyServiceName.
Created attachment 125025 [details] Annotations Suite
It took me a while, but I made it work. The thing I think I was missing was that I had moved my annotation processor to a Java class library project which no longer had "@ServiceProvider(Service=Processor.class)", so the "META-INF/services/javax.annotation.processing.Processor" file wasn't in the JAR. The annotation processor was still working, but presumably the service file is required for NetBeans to take the extra step of noticing the generated class. I built the JAR by hand from the Annotations Module build directory, but my MANIFEST.MF is much simpler than yours. How did you build your annotations.jar file?
>How did you build your annotations.jar file? I let the IDE built it and then copy it to /tmp and point the New Library Wrapper Module Wizard to this copy. It was copied by the wizard into the new library wrapper project.
Integrated into 'main-golden', will be available in build *201210010929* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/2ecb86354a59 User: Tomas Zezula <tzezula@netbeans.org> Log: #216994:A public class generated by an annotation is not visible outside its module.