Important: The information in this document is obsolete and should not be used for new development.
This appendix lists some of the build settings you are likely to use in Java-based projects. See the Project Builder release notes for a complete treatment of Project Builder’s build settings.
Table A-1 describes build settings that apply to a project as a whole; that is, they apply to all targets in a project.
Build setting | Description |
|---|---|
| Name of the project. This setting is read-only. |
| Base location for built products. Configured initially as |
| Base location for the temporary files generated by a project’s targets. Default: |
| The location for products. Set initially to |
| The base location for all products. Configured initially as |
Table A-2 describes build setting that determine the location of an installed product and its permissions.
Build setting | Description |
|---|---|
| Base location for the installed product. Default: |
| Location of the installed product. For example, |
| Fully qualified path for the installed product. By default, it concatenates |
| Determines whether the target’s product gets installed. When undefined, which is the default, the target’s product gets installed. |
| When |
| User who owns the generated product. As |
| Group who owns the generated product. Usually, staff. This is applied after the product is deployed. |
| The mode that is applied to the product after it’s deployed. Default: |
Table A-3 describes build settings that identify a target and determine the location of source files and of a directory for temporary files created as a product gets built.
Build setting | Description |
|---|---|
| Name of the target. This setting is read-only. |
| Name of the product the target builds. This setting is read-only. |
| The action being performed on the target. Values: |
| The base location of project sources. It’s set to the contents of the |
| The base location for intermediate build files. Configured initially as |
| The location of a target’s intermediate files. Configured initially as |
Table A-4 describes build settings that determine the flags that are used in the invocation of the Java compiler as well as the location of generated Java class files.
Build setting | Description |
|---|---|
| The base location for Java class files. Configured as |
| The compiler used in Sources (compilation) build phases. Initially configured as |
| Determines whether Java classes are compiled with debugging symbols. When |
| Determines whether the compiler generates warnings. When |
| Determines whether the compiler shows a description of the use of deprecated API (whether the |
| Determines the target Java virtual machine for generated class files ( |
| Determines the value for the |
| Use to set compiler options not supported in build settings for |
| Base |
| Base |
| Space-separated list of paths of required JAR files. This list is added to the |
| Colon-separated list of additional paths of required JAR files. This list is added to the |
| Space-separated list of required JAR files. Initially configured as the combination of |
Table A-5 describes build settings that determine whether Java class files are archived, how they are archived, and the name of the archive file, among other items.
Build setting | Description |
|---|---|
| Determines the disposition of Java class files generated by the target. This setting can have two values, |
| Determines whether the contents of the archive file are compressed. When |
| Determines the extension used for the JAR file. Values: |
| Project-directory based path to the file used to supplement the default manifest file ( |
| Path to the Cocoa application stub that’s embedded in a bundle-based Java application to launch the Java application. Configured as |
| Path to the development-settings property list file of the product. Initially configured as |
Last updated: 2003-10-10