blob: 24cc74a4e5015d593aa8732a08e3e2adcd1043fa [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. 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">
<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>Java projects</title>
</head>
<body>
<h1>Java projects</h1>
<p>A Java project contains source code and related files for building a Java
program. It has an associated Java builder that can incrementally compile Java source files as they are changed.</p>
<p>A Java project also maintains a model of its contents. This model
includes information about the type hierarchy, references and declarations of Java elements.
This information is constantly updated as the user changes
the Java source code. The updating of the internal Java project model is independent of the
Java builder; in particular, when performing code modifications, if auto-build is turned
off, the model will still reflect the present project contents.</p>
<p>You can organize Java projects in two different ways:</p>
<ul>
<li><span>Using the project as the source container. This is the recommended organization for simple projects.</span></li>
<li><span>Using source folders inside the project as the source container. This is the recommended organization for more complex projects. It allows you to subdivide packages into
groups.</span></li>
</ul>
<p><img src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
<p>
<a href="../concepts/concepts-4.htm">Java builder</a><br></p>
<p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
<p>
<a href="../reference/ref-121.htm">New Java Project wizard</a></p>
</body>
</html>