AnnotationProcessingQuery.Result should be able to specify a Map<String,String> processorOptions corresponding to the -A options passed to javac.
Marking P2 because it will be harder to change the API after a release. Anyway it should be simple to implement.
Created attachment 94730 [details]
[JG01] Should not be marked as compatible when you are adding an interface method. Of course this is prerelease code.
[JG02] processorOptions Javadoc should be clear that values can be null, as specified in ProcessingEnvironment.getOptions. (Would be good to link to that Javadoc BTW.)
When in main-silver I will update the impl in contrib/autoproject.java, which should be an easy change (am already sniffing -A options from javac).
(In reply to comment #2)
> [JG01] Should not be marked as compatible when you are adding an interface
> method. Of course this is prerelease code.
I think that the incompatible flag should be used when doing change incompatible with previous release(s), not doing incompatible changes to API introduced in the same release.
> When in main-silver I will update the impl in contrib/autoproject.java, which
> should be an easy change (am already sniffing -A options from javac).
I think that contrib/autoproject can be updated anytime, even before this change is part of main-silver (the method will never be called before that, but should not cause any problems, AFAIK).
Fixed in jet-main.
Integrated into 'main-golden', will be available in build *201003050200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Dusan Balek <email@example.com>
Log: Issue #181421: Missing support for annotation processor options (-Akey=value) added