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.
I would like to introduce JavaClassPathConstants.PROCESSOR_PATH. This would be key for ClassPath.getClassPath for the Java processor path.
Created attachment 89175 [details] Proposed patch.
Please review.
OK for me. Maybe we should also create aliases for old ClassPath constants in the JavaClassPathConstants and possibly deprecate the ClassPath constants. class JavaClassPathConstants { psf String COMPILE = CP.COMPILE; .... } But this is unrelated to this API review.
VS01: What is the relation of JCPC.PROCESSOR_PATH to scanning? Do we need to update JavaPathRecognizer? Pardon my ignorance, but I just don't know what java processor is and what sort of classpath it needs. re. ClassPath constants - Deprecating those would be very useful. People tend to thing that these constants can be used for all languages/project types, but they are only for java and java based projects. But as tzezula says this is not part of this API change.
VS01: Sorry, I should have been more clear and precise: it is a classpath on which Java annotation processors are being searched. It corresponds to javac -processorpath. I currently do not see a reason to index roots on this classpath.
VS01: I see, ok, thanks.
Looks OK to me.
Thanks for the review.
Integrated in jet-main: http://hg.netbeans.org/jet-main/rev/c4005287acdf
Integrated into 'main-golden', will be available in build *200910221401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/c4005287acdf User: Jan Lahoda <jlahoda@netbeans.org> Log: #174202: introducing JavaClassPathConstants.PROCESSOR_PATH.