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.
Summary: | Java language support for JSR 292 | ||
---|---|---|---|
Product: | java | Reporter: | jrose <jrose> |
Component: | Editor | Assignee: | Dusan Balek <dbalek> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | Macintosh | ||
OS: | Mac OS X | ||
URL: | http://hg.openjdk.java.net/mlvm/mlvm/langtools | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
jrose
2009-01-21 18:46:54 UTC
RFEs like this should eventually be addressed by referring language questions to javac itself. Now, I put my special javac.jar on the bootclasspath of the javac command which ant uses to build the project which uses the extended language features. I can do this easily by adding a line like this to nbproject/project.properties : javac.compilerargs=-Xlint:unchecked -J-Xbootclasspath/p:${reference.langtools-javac.jar} -XDinvokedynamic Ideally, these special options, along with the special jar, should (somehow) be absorbed into the NetBeans editor, and used to perform all sorts of textual analysis of the Java code which will be compiled by that special javac. I think the javac guys are eager to work on this; it's certainly better than writing half of your own compiler (or forking the code). For the moment, since the new features are used infrequently so far, I'd be happy with the partial solutions outlined in the previous comment. |