blob: 5e62e16b87b2c393381ceb921b32d0f7a353a48d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) GK Software AG and others 2012. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>Improving Java code quality</title>
</head>
<body>
<h1> Improving Java code quality </h1>
<p>
The Eclipse Java compiler performs more checks and analyses than are mandated by the Java Language Specification.
This is done in order to help you to improve the quality of your Java code.
Since different users have different views of which warnings are interesting, this behavior is highly configurable.
See <a href="../reference/preferences/java/compiler/ref-preferences-errors-warnings.htm">Java Compile Errors/Warnings Preferences</a>
for available options.
</p>
<p>
Some warnings and errors should be obvious and generally valid for everybody.
In some cases you may want to configure the compiler to match your code style
and also your quality goals.
Some analyses are most helpful if you to some degree adjust your code style
to make it better analyzable by the compiler.
</p>
<p>
The pages listed below give some background on certain analyses and hints
on how to make the best use of them:
</p>
<ul>
<li><a href="task-using_null_annotations.htm">Using null annotations</a></li>
</ul>
</body>
</html>
|
