This is a feature of JBuilder Professional and Enterprise
The Import Project wizard creates a new JBuilder project from an existing body of work, deriving needed paths from the directory tree.
The Import Project wizard creates a JBuilder project file, which has a .jpr
or .jpx
file extension. The two types are interchangeable except in team development, when you must use a .jpx
project file type.
The project file contains the project settings and a list of all the files added to the project. Project settings will vary according to the type of project you create, but can include directory structure, paths to libraries, sources, JDK versions, and relevant deployment settings. JBuilder uses the list of files and the project settings whenever you load, save, change, build, or deploy a project.
You don't edit a project file directly, but it is modified whenever you use the JBuilder development environment to add or remove files or to set other options. You can see the project file as the top node of the project tree in the project pane.
JBuilder supplies paths based on information it finds when it scans the directory tree; this wizard requires you to check those paths before finishing. Fill in the fields in Step 1 then click Next to go to Step 2 and examine your paths.
Click the ellipsis button (...) to browse to the directory you plan to use as the root directory of the new project. This is called the working directory or the project directory (these two terms are synonymous.)
Using this directory as the root, JBuilder scans the directory tree for source paths, output paths, backup paths, and so on. These paths are displayed in Step 2, where you can approve, add to, or change them.
Set the name and type of the project file JBuilder creates. The default name is untitled
. The default type is .jpx
. Use the .jpx
project file type for shared projects. Use either project file type for projects that aren't shared by other JBuilder users.
Sets the project you want to use as a template for the present project. This sets the default paths and directories. All paths and names can be changed in the wizard; this only sets default behavior.
jbproject
directory in your home directory, and makes your source, backup, documentation, and output directories the descendants of your project directory.There are two ways to choose a template:
This is an HTML file with the same name as the project file. It has information about the project (author, company, description of the project) that goes into the About box. It can also be used to keep track of your to do items once the project is created. You can choose whether the project information you enter in this wizard will be commented into the head of each file other wizards generate for the project.
Set your paths in Step 2.
Note: All paths on this page can be changed at any time in the Paths page of the Project Properties dialog box (Project|Project Properties.)
JBuilder sets suggested project, source, backup, documentation, and output paths. If need be, you can edit these fields directly or click the ellipsis buttons (...) to browse to other locations.
The version that ships with JBuilder is set by default.
To compile against another JDK, click the ellipsis button (...) to open the Select A JDK dialog box. Within this dialog, either browse to a registered JDK location or else click New to open the New JDK Wizard, from which you can set a path to a different JDK.
The output path stores generated files and defined resource files. Edit the field directly or click the ellipsis button to browse to the desired path.
To define individual files and project-wide file types as resources, see Build page: Resource tab.
The backup path stores backup versions of files. Edit the field directly or click the ellipsis button to browse to the desired path.
Set the number of backup levels from the Editor page of the Editor Options dialog box (Tools|Editor Options.) The default level is 5. The maximum is 90.
This is also known as the project directory. It has the same name as the project file.
It's generally the parent directory of the source directory. It's often the parent directory of the output, backup, documentation, and library directories, but whether this is the case for the new project depends on the directory structure the project is created from and on the choices you make here in Step 2.
The Source, Documentation, and Required Libraries pages each have a column of buttons on the right.
Provides a browser that lets you choose or enter a new path. The new path is added to the bottom of the list.
Provides a browser that lets you change the selected path.
Removes the selected path from the list.
This does not remove that directory or otherwise affect your directory tree, it only removes it from the search list.
Change the position of the selected path by one step up or one step down for each click. This changes the order in which the paths are searched.
This does not change the location of the directories, it only changes the order in which JBuilder searches them.
Resets this list to the state it was in when the dialog box was opened.
Set default and test source paths on the Source page. It's possible to choose the same path for both functions, though not recommended.
The default source path is used by wizards that create source files. Adding additional source paths means the project works with multiple source roots. Note that imports automatically select all the source directories as source roots.
Note: JBuilder uses the path you set for the purpose specified. However, if JBuilder can't find the specified source path, it will go through the list of available paths from the top down. Sort your paths to control which one is searched first in this case.
Unit Testing and the Test path are features of JBuilder Enterprise. The test path is used as the source path when you use JBuilder's unit testing features. This provides the option of using a different area for testing so you can easily separate your tests from your other code. This is most useful in deployment.
Displays the path or paths that contain the HTML documentation files for the JDK selected in the JDK field. This allows reference documentation to be displayed in the doc view in the content pane.
Sets the libraries needed by the project at runtime.
If necessary, add libraries or make new ones. Click Add to browse to an existing library in the Select One Or More Libraries dialog box. You can click New in this dialog to bring up the New Library Wizard.
There are three possible colors for libraries listed:
Colors in library lists
Color | Description | Troubleshooting |
---|---|---|
Black | The library is defined correctly. | |
Red | The library definition is missing. | This typically means the project refers to a library that is not yet defined. It can also mean the library has been defined without any paths. |
Gray | Use of this library requires an upgrade. | You need to upgrade your edition of JBuilder in order to use this library. For example, if you have JBuilder Personal, use of the dbSwing library requires that you upgrade to either JBuilder Professional or Enterprise. |
It's possible to click Finish in Step 2.
This information can later be changed on the General page of the Project Properties dialog box (Project|Project Properties).
Encoding determines how JBuilder should handle characters beyond the ASCII character set. The default is your platform's default encoder.
Choose this if you want assert
recognized as a keyword and enable JDK 1.4-style assertions. assert
takes a boolean
value and checks a state before the associated statement is executed.
This is a feature of JBuilder Professional and Enterprise.
This option is checked by default. It makes several things happen:
Note: Not all packages are displayed, only a logical subset determined by how deeply you tell JBuilder to expose packages.
JBuilder exposes packages to the level you set, unless adding more levels to a particular package won't change the length of the overall package list.
This is the information that shows in the About box for your application. If you use a wizard that generates header comments, this information also goes into the header comments when that wizard's Generate Header Comments option is checked. These fields must be edited before using a wizard for the Javadoc comments to appear at the beginning of the class files.
Select a field to edit and enter the appropriate text in the Text column.
This is a feature of JBuilder Professional and Enterprise.
Check this option if you want to be able to find references in any of the project libraries. It's unchecked by default.
Checking this means that: