Build: NetBeans IDE 7.3 (Build 201302132200)
VM: Java HotSpot(TM) Client VM, 23.7-b01, Java(TM) SE Runtime Environment, 1.7.0_17-b02
gorrus: during external build
java.io.FileNotFoundException: JAR entry META-INF/services/org.openide.filesystems.URLMapper not found in /ssd/work/cnd-main/nbbuild/netbeans/ide/modules/org-netbeans-modules-web-common.jar
Created attachment 133977 [details]
The comment "during external build" makes me believe that there was a build in progress which might delete or create or rewrite some external JAR files while the IDE's processor tried to parse (and also use annotation processor) an such JAR files.
Certainly the annotation processor is allowed (and even required) to fail in case when somebody modifies/removes libraries underneath.
The Javac parser should then report the exception as low priority one, right? But it seems the exception has been reported and I don't think there is anything else to do. Closing.
Passing to Javac for review of my closing action.
(In reply to comment #2)
> The Javac parser should then report the exception as low priority one, right?
In this case, it appears MetaInfServicesLookup.search reports the exception into a Logger itself (line 358 in my sources). I don't think there is a way for us to create a brand new Logger hierarchy for stuff inside an annotation processor. So this appears to be completely out of our control.
> But it seems the exception has been reported and I don't think there is
> anything else to do. Closing.
> Passing to Javac for review of my closing action.
I wonder why the AP does so much work. Background scan is claimed to be "slow", but the NB platforms APs are not really helping in making it fast, when they are partially starting another IDE instance while processing the annotations. I would suggest to make the AP be faster by making it do only what it really needs to do, which would also make it much less probable any problems like this will appear.