General page (Project Properties dialog box)

The General page of the Project Properties dialog box sets the following options:

Encoding

Specifies the encoding that controls how JBuilder interprets text files containing characters beyond the ASCII character set. If no setting is specified, the default file-encoding converter for the platform is used. For more information, see the Specifying a native encoding for the compiler topic in the "Internationalizing programs with JBuilder" chapter of Building Applications with JBuilder.

For a list of the valid encodings, see "Internationalization Tools: native2ascii".

Enable Assert Keyword

Choose this option if you want assert recognized as a keyword. JBuilder supports JDK 1.4 assertions.

Previous to JDK 1.4, assert was a keyword reserved for future use. In JDK 1.4, the assert keyword has been added to the language and is used in the assertion facility.

See also

Automatic Source Packages

This is a feature of JBuilder SE and Enterprise.

Enable Source Package Discovery And Compilation

When this option is enabled, all packages in the project's source path automatically appear in the project pane. When building with this option on, any packages that contain buildable files are automatically built and copied, with any resources, to the project's output path. For example, if a project contains Java and SQLj files, the Java files are compiled and SQLj is run against any SQLj files. To set individual files and project-wide file types as resources, see Build page: Resource tab.

The Enable Source Package Discovery And Compilation option is on by default.

To minimize the number of package nodes listed, JBuilder automatically displays a subset of the packages in your project. This subset is carefully chosen to give you access to all your source by browsing through subpackages of the packages listed. Even though some source packages may not be listed at the top level of your project, JBuilder still builds them.

Important: After adding new source files to the project, select the refresh button on the project toolbar to update the automatic source package list.

A <Project Source> node also displays at the top of the project pane when the automatic source packages feature is enabled. This node contains all the source packages and source files in the project, except packages and files that have been added manually. You can use this node to quickly filter source packages. See "Filtering packages" for more on filtering.

This option must be enabled to use the package filtering feature.

See also

Deepest Package Exposed

Determines which packages are displayed by JBuilder in the project pane. Packages that consist of the specified number or fewer subpackage names are included. JBuilder uses longer package names only if it does not increase the length of the package list. Expand the package node to view the other packages.


The default setting is 3.

Note: This setting also affects the display of enabled packages in the project pane when filtering is applied. If you have deeply nested packages and are excluding only a few packages, it's recommended that you increase the number in the Deepest Package Exposed field so more packages are displayed in the project pane.

For example, a project contains the following files:

com/whizco/Utility.java
com/whizco/sample/EntryForm.java
com/whizco/sample/shared/DatabaseAccess.java
com/whizco/other/package/LegacyIntegration.java

The default setting of 3 would display this list:

com.whizco  (only 2 packages, but because it contains files, it must be listed)
com.whizco.sample  (contains both source and other subpackages)
com.whizco.other.package (lists 4 packages, because listing 3 wouldn't make the list any shorter)

A setting of 1 would display this:

com.whizco (listing only com would not shorten the list)

A setting of 2 would display this list:

com.whizco

A setting of 4 would display this list:

com.whizco
com.whizco.sample
com.whizco.sample.shared
com.whizco.other.package

Note: Packages com and com.whizco.other are not listed, because they do not contain any source or resources.

Class Javadoc Fields

Specifies the Javadoc tags generated in the class files when the Generate Header Comments is enabled in a wizard. Edit the Label and Text fields by selecting a field and typing. These fields must be edited before using a wizard for the Javadoc comments to appear at the beginning of the class files.

Include References From Project Library Class Files

This is a feature of JBuilder SE and Enterprise.

Includes references from all of the project libraries. When this option is checked, the Find References command on the editor's context menu finds all source files that use a given symbol, including within the project libraries. Find References is a feature of JBuilder SE and Enterprise.

Also, when this option is checked, the project's UML diagrams include any references from the project libraries. UML is a feature of JBuilder Enterprise.

See also

Reset

Resets everything to the state they were in when the dialog box was displayed.