Build page (Project Properties dialog box)

Use the Build page of the Project Properties dialog box to set compiler options.

Choose Project|Project Properties and click the Build tab. You can also right-click the project file in the project pane and choose Properties.


Java

To set compiler options for the current project, select the Java tab of the Build page. The options are applied to all files in the project, as well as to files referenced by these files, stopping at packages which are marked "stable."

To set these options for all new projects, choose Project|Default Project Properties and click the Build tab.

See also:
Building Applications with JBuilder:
Setting compiler options
"How JBuilder constructs paths"
"How JBuilder finds files when you compile"

Default Compiler Options

Include Debug Info
Includes symbolic debug information in the .class file when you compile, make, or rebuild a node.
Show Warnings
Displays compiler warning messages.
Show Deprecations
Displays all deprecated classes, methods, properties, events, and variables used in the API. When a warning is displayed that deprecated APIs were used, turn this option on to see specifically what is deprecated.
Synchronize Output Dir
Deletes class files on the out path that you don't have source files for before compiling. The out path directory is specified in the Output Path field on the Paths page of the Project Properties dialog box. The location of source files are specified on the Source tab of the Paths page.
Check Stable Packages
Checks files in the packages that are marked "stable" to see whether they and their imported classes need to be recompiled. This option shortens the edit/recompile cycle by not re-checking stable packages.

If this option is off, a given branch of the checking process halts when it reaches a package marked "stable;" it does not look for unstable packages imported by the stable packages. Therefore, with this option, you might need to specify a greater number of modules to compile.

By default, the compiler checks packages marked "stable" as well as packages marked "unstable," to determine whether they and their imported classes need to be recompiled.

Make Stable Packages
If this option is on, the compiler will compile or check all the classes of a package on the first build and mark the package "stable." If this option is off, only the referenced classes of this package will be made, and the package will not be marked "stable."

This option should be off when working with partial projects.

This option is especially useful for working with a library of classes with no source available, when some of the class files are not consistent, but not used.

Obfuscate
Obfuscation makes your programs less vulnerable to reverse engineering. After decompiling your obfuscated code, the generated source code contains altered symbol names for private symbols.
Exclude Class
Excludes the selected .class file from a compile.

For example, excluding class A removes all calls to "static void" methods of A from OTHER classes. These are some of the implications:

If you compile and run it, you will get the expected behaviour. If you compile it after excluding class Asserts the COMPLETE call to Assert will be removed from your code, including incrementing "i", which will print the "OOPS".

One side effect is that the thread executes faster without the Assert which may expose problems in other parts of the code. If you construct the message during the call (Assert(test, "Number of Arguments = " + args.length)), it may run faster after excluding Asserts, because constructing the String takes some time.

Autosave All Files Before Compiling
Automatically saves all files in the project before each compile.
To Output Path
Causes source code generated from an RMI or IDL file during a make to be saved in the out path. The out path is specified in the Output Path field on the Paths Page of the Project Properties dialog box and defaults to the /[home]/[username]/jbproject/[project-folder-name]/classes folder.


IDL

This is a feature of JBuilder Enterprise.
To set these options for the current project, choose Project|Project Properties, then select the Build tab, then the IDL tab.

To set these options for all new projects, choose Project|Default Project Properties, and select the Build tab.

IDL Compiler

Select one of the following options from the list. In order for JBuilder to work with the selected IDL compiler, you must first set up the ORB for use with JBuilder by selecting the CORBA tab Tools|Enterprise Setup. If you have added a different ORB in the Enterprise Setup wizard, it will display as an option here.

Generated Code Options

Package
Code is generated in the specified package. The package name for definitions is prepended with the specified package name. If a directory with the specified package name does not exist, it will be created. If the package directory exists, its contents will be updated. code is generated that uses CORBA package resolution rules.
Include Path
Specifies the location where other files that are referenced from IDL files reside. Click the ellipsis button beside this field to open a dialog box that lets you browse the directory structure for the location of the files.

In the example below, the include directory should point to the location where the howdy.idl file can be found.


#include "howdy.idl"
module x {
     interface P {
          string getThis();
     };
};
Additional Options
Here is where you enter any additional options for your IDL compiler, as you would enter them when running the compiler from the command line.
Symbols Defined For Conditional IDL Compilation
Lists the symbols that have been defined for conditional IDL compilation. Click the New button to display the Input dialog box, where you can define a new conditional symbol. To remove a symbol from the list, select it then choose the Delete button.

Reset

Select Reset to undo any changes made to this dialog during this session.


WebLogic

This is a feature of JBuilder Enterprise.
The WebLogic tab allows you to specify options for building an EJB group if the WebLogic Server is your target application server.

Use WebLogic EJBC To Generate Stub Files

Selecting this option invokes the WebLogic ejbc.exe, which generates a JAR file from the EJB group JAR file that contains the compiled stub files. This JAR is then ready for deployment. This compilation process is slow, so you might not want to select this option until you're ready to deploy.

Like other project settings, setting this option affects just your current project.

Use External Compiler To Compile Stub Files

Select this option when you are using ejbc.exe, but you want to specify an external compiler to compile the stub files. You then specify the compiler of your choice in the Compiler Path field. You might choose this option to specify a quicker compiler.

Choosing an external compiler is a global setting that will affect all your projects.

Compiler Path

Specify the path and name of the external compiler you wish to use. This option is enabled only when the Use External Compiler To Compile Stub Files option is selected.