Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
View | Details | Raw Unified | Return to bug 369246
Collapse All | Expand All

(-)a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm (-2 lines)
Lines 1461-1468 Link Here
1461
current location. Such a default may be effective by enabling the option
1461
current location. Such a default may be effective by enabling the option
1462
<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NONNULL_IS_DEFAULT">COMPILER_NONNULL_IS_DEFAULT</a> or by using the annotation specified by the option
1462
<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NONNULL_IS_DEFAULT">COMPILER_NONNULL_IS_DEFAULT</a> or by using the annotation specified by the option
1463
<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NONNULL_BY_DEFAULT_ANNOTATION_NAME">COMPILER_NONNULL_BY_DEFAULT_ANNOTATION_NAME</a>.
1463
<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NONNULL_BY_DEFAULT_ANNOTATION_NAME">COMPILER_NONNULL_BY_DEFAULT_ANNOTATION_NAME</a>.
1464
Insufficient nullness information is usually a consequence of using other unannotated
1465
variables or methods.
1466
<p>The compiler options <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NONNULL_ANNOTATION_NAME">COMPILER_NONNULL_ANNOTATION_NAME</a> and
1464
<p>The compiler options <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NONNULL_ANNOTATION_NAME">COMPILER_NONNULL_ANNOTATION_NAME</a> and
1467
   <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NULLABLE_ANNOTATION_NAME">COMPILER_NULLABLE_ANNOTATION_NAME</a> control which annotations the compiler
1465
   <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_NULLABLE_ANNOTATION_NAME">COMPILER_NULLABLE_ANNOTATION_NAME</a> control which annotations the compiler
1468
   shall interpret as nonnull or nullable annotations, respectively.
1466
   shall interpret as nonnull or nullable annotations, respectively.
(-)a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm (-3 / +22 lines)
Lines 777-782 Link Here
777
		</td>
777
		</td>
778
		<td valign="top">
778
		<td valign="top">
779
		<p>When enabled, the compiler will issue an error or a warning when it encounters that a local variable which is certainly null is dereferenced. Note that the analysis can not find all null pointer accesses, see <strong>Potential null pointer access</strong>.</p>
779
		<p>When enabled, the compiler will issue an error or a warning when it encounters that a local variable which is certainly null is dereferenced. Note that the analysis can not find all null pointer accesses, see <strong>Potential null pointer access</strong>.</p>
780
		<p>This diagnostic can also be enabled for fields using the option <b>Include fields in null analysis</b>.</p>
780
		</td>
781
		</td>
781
		<td valign="top">
782
		<td valign="top">
782
		<p>Warning</p>
783
		<p>Warning</p>
Lines 788-793 Link Here
788
		</td>
789
		</td>
789
		<td valign="top">
790
		<td valign="top">
790
		<p>When enabled, the compiler will issue an error or a warning when it encounters that a local variable which may be null is dereferenced. Note that the analysis is fairly conservative, it only considers cases where there is something suspicious.</p>
791
		<p>When enabled, the compiler will issue an error or a warning when it encounters that a local variable which may be null is dereferenced. Note that the analysis is fairly conservative, it only considers cases where there is something suspicious.</p>
792
		<p>This diagnostic can also be enabled for fields using the option <b>Include fields in null analysis</b>.</p>
793
		<p>The quality of the analysis can be improved by using null-annotations, which can be enabled using the option 
794
		<b>Enable annotation-based null analysis</b>
791
		</td>
795
		</td>
792
		<td valign="top">
796
		<td valign="top">
793
		<p>Ignore</p>
797
		<p>Ignore</p>
Lines 799-807 Link Here
799
		</td>
803
		</td>
800
		<td valign="top">
804
		<td valign="top">
801
		<p>When enabled, the compiler will issue an error or a warning whenever a local variable which can not be null is tested for null.</p>
805
		<p>When enabled, the compiler will issue an error or a warning whenever a local variable which can not be null is tested for null.</p>
806
		<p>This diagnostic can also be enabled for fields using the option <b>Include fields in null analysis</b> below.</p>
802
		</td>
807
		</td>
803
		<td valign="top">
808
		<td valign="top">
804
		<p>Ignore</p>
809
		<p>Ignore</p>
810
		</td>
811
	</tr>
812
	<tr>
813
		<td valign="top">
814
		<p>Include fields in null analysis</p>
815
		</td>
816
		<td valign="top">
817
		<p>When enabled, the compiler will raise null analysis based errors or warnings on fields.</p>
818
		<p>These diagnostics can be configured using the options <b>Null pointer access</b>, 
819
		<b>Potential null pointer access</b> and <b>Redundant null check</b>.
820
		</td>
821
		<td valign="top">
822
		<p>Off</p>
805
		</td>
823
		</td>
806
	</tr>
824
	</tr>
807
	<tr>
825
	<tr>
Lines 870-879 Link Here
870
	</tr>
888
	</tr>
871
	<tr>
889
	<tr>
872
		<td valign="top" style="padding-left: 2em;">
890
		<td valign="top" style="padding-left: 2em;">
873
		<p>Use non-null as workspace-wide default</p>
891
		<p>Use non-null as workspace-wide (or project-wide) default</p>
874
		</td>
892
		</td>
875
		<td valign="top">
893
		<td valign="top">
876
		<p>When enabled, this option globally achieves the same effect as specifying <b>'NonNull' annotation</b> does for individual elements.</p>
894
		<p>When enabled, this option globally (at a workspace level or project level depending on
895
		where the option is configured) achieves the same effect as specifying <b>'NonNull' annotation</b> does for individual elements.</p>
877
		</td>
896
		</td>
878
		<td valign="top">
897
		<td valign="top">
879
		<p>Off</p>
898
		<p>Off</p>
Lines 937-943 Link Here
937
		</td>
956
		</td>
938
		<td valign="top">
957
		<td valign="top">
939
		<p>When enabled, the compiler will issue an error or a warning when a non-null annotation is applied although the same effect is already achieved by a default applicable at the current location. 
958
		<p>When enabled, the compiler will issue an error or a warning when a non-null annotation is applied although the same effect is already achieved by a default applicable at the current location. 
940
		Such a default may be set by enabling the option <b>Use non-null as workspace-wide default</b> or by using the annotation specified by the option <b>'NonNullByDefault' annotation</b>.</p>
959
		Such a default may be set by enabling the option <b>Use non-null as workspace-wide (or project-wide) default</b> or by using the annotation specified by the option <b>'NonNullByDefault' annotation</b>.</p>
941
		</td>
960
		</td>
942
		<td valign="top">
961
		<td valign="top">
943
		<p>Warning</p>
962
		<p>Warning</p>

Return to bug 369246