JBuilder® 2007 Migration Guide

Thank you for purchasing JBuilder 2007!

This guide is a quick reference that describes how to import your previous JBuilder projects into JBuilder 2007. The first part of this file contain general migration information and a step-by-step procedure. The second section of this document discusses the differences between previous versions of JBuilder and JBuilder 2007. It includes comparisons of the Dialogs and Menu commands in each. This information is also available in the online help within JBuilder 2007.

JBuilder Project Migration Overview

You can import any type of Java project created in a previous release of JBuilder into the JBuilder 2007/ workspace, including Java SE (formerly J2SE) projects, Java EE (formerly J2EE) projects, VisiBroker projects, and RMI/JNI projects. Projects can be under source control. If the JBuilder project is under source control, the import wizard may be able to check it into the JBuilder 2007/ workspace.

The project import does not copy the JBuilder source files and folders directly into the JBuilder 2007/ workspace, but creates a link using the resource link capability. The project file in the workspace maps a resource name, for example, /src, to an absolute path name, for example, C:/MyProject/src/java. New files that are added to the project are added to the original source folder.

The following files and folders are created in the workspace folder for a project imported from a previous version of JBuilder:

.classpath: The linked resources file (XML source).
.project: The Java project file (XML source).
/bin: The output folder.

Warning:	If the Enabled Linked Resource option on the Linked Resources page of the Preferences dialog box (WindowPreferencesGeneralWorkspaceLinked Resources) is off, the project import may fail. If this happens, the following message will be displayed in the Import Status dialog box: Error creating source path link for <project name>. Linked resources are not supported by this application.

The build process uses the standard JDK compiler, not the previous JBuilder compiler, Borland Make for Java. Before you build your imported project, you can check compiler options on the Java Compiler page of the Properties dialog box.

Projects with Generated Source

When a project, such as a VisiBroker or RMI project, has auto-generated sources that are output to the /Generated Sources folder in the classes folder, the /Generated Sources folder is not imported. However, when you build the project the source files are automatically generated and placed in a /Generated Sources folder in the workspace. The Derived setting on the Info page of the Properties dialog box (PropertiesInfo from the context menu in the Package Explorer with the folder selected) indicates that this folder is auto-generated.

Unsupported Properties

Some project properties are not supported in or are translated to the equivalent on import. The following table illustrates those items:

Project Item	Description
/Additional Settings Folder	Not imported; no equivalent.
/doc Folder	Not imported. Regenerate with FileExportJavadoc.
/bak Folder	Not imported.
jbInit() Method	Left in code.
@todo Tags	Left in code.

Setting Import Properties

Before importing JBuilder J2EE or VisiBroker project, you need to configure application server and VisiBroker locations.

To set properties for importing J2EE projects

From the workbench click File Import.
Click the J2EE node and select from the following import file options:

App Client JAR file
EAR File
J2EE Utility JAR
RAR file

After selecting the import file click Next, and follow the prompts to complete the import properties configuration.

To set properties for JBuilder VisiBroker project imports

Open the VisiBroker page of the Preferences dialog box (WindowPreferencesVisiBroker).
Enter the directory where VisiBroker tools are installed in the VisiBroker Tools Directory field. Typically, this is bin folder of your Borland Enterprise Server installation.
Click Apply and OK to save your settings.
Open the Builders page of the Properties dialog box (ProjectPropertiesBuilders). Make sure the VisiBroker Builder option in the Configure The Builders For This Project list is selected.
Click OK to save your settings.

Importing a Project from a Previous Version of JBuilder

You can import any type of Java project created with a previous version of JBuilder into the JBuilder 2007/ workspace.

To import a Java project from JBuilder

Choose FileNewProject to display the New Project wizard.
Open the Legacy JBuilder folder from the Wizards list and choose Java Project(s) from Existing JBuilder Project. Click Next to display the Import JBuilder Project wizard.

Note:	You can also choose FileImport...Legacy JBuilderJava Project(s) from Existing JBuilder Project.

Enter the name and path to an existing JBuilder project in the JBuilder Project File field. Use the Browse button to display the Open dialog box where you can browse to the JBuilder project file. The file extension must be .jpx. When you select a valid JBuilder project name, the Project Name field is filled in automatically.
The default user home directory is displayed in the User Home Directory field. This is based on the default installation directory for JBuilder and defines the default search directory for libraries.
The list of directories to search for JBuilder libraries for the selected project is displayed in the Library Search Directories list.

Click the Add button to add directories to the search field. The Browse for Folder dialog box, where you can browse to the library search directory, is displayed.
Select a directory and click the Remove button to remove a search directory from the list.

Libraries required by the selected project but not yet located are displayed in the Libraries Not Yet Found list. You must locate the library directory for each library and add it to the Library Search Directories list.
Click the Enable VCS Plugin For This Project option if the project is under source control in JBuilder and you want the project checked out. You may need to log onto the server to check out the project. The project is checked out into the workspace.

Warning:	CVS and Subversion projects that are checked into a local repository cannot be checked out.

Click Finish to import or check out the project.

Note:	The Import Status dialog box is displayed if there are import warnings or errors. Click the Details button for more information. Typically, warnings or errors are displayed if an unsupported JBuilder project node or folder exists in the imported project. Click the OK button to close the dialog box.

If you are not already in the Java perspective, the Open Associated Perspective dialog box is displayed where you can choose to go the Java perspective and edit code.

To import a Java J2EE project from JBuilder:

Choose FileNewProject to display the New Project wizard.
Open the Legacy JBuilder folder from the Wizards list and choose Java EE Project(s) from Existing JBuilder Project. Click Next to display the Import JBuilder Project wizard.

Note:	You can also choose FileImport...Legacy JBuilderJava EE Project(s) from Existing JBuilder Project.

Enter the name and path to an existing JBuilder project in the JBuilder Project File field. Use the Browse button to display the Open dialog box where you can browse to the JBuilder project file. The file extension must be .jpx. When you select a valid JBuilder project name, the Project Name field is filled in automatically.
The default user home directory is displayed in the User Home Directory field. This is based on the default installation directory for JBuilder and defines the default search directory for libraries.
The list of directories to search for JBuilder libraries for the selected project is displayed in the Library Search Directories list.

Click the Add button to add directories to the search field. The Browse for Folder dialog box, where you can browse to the library search directory, is displayed.
Select a directory and click the Remove button to remove a search directory from the list.

Libraries required by the selected project but not yet located are displayed in the Libraries Not Yet Found list. You must locate the library directory for each library and add it to the Library Search Directories list.
Click the Enable VCS Plugin For This Project option if the project is under source control in JBuilder and you want the project checked out. You may need to log onto the server to check out the project. The project is checked out into the workspace.

Warning:	CVS and Subversion projects that are checked into a local repository cannot be checked out.

Click Finish to import or check out the project.

Note:	The Import Status dialog box is displayed if there are import warnings or errors. Click the Details button for more information. Typically, warnings or errors are displayed if an unsupported JBuilder project node or folder exists in the imported project. Click the OK button to close the dialog box.

If you are not already in the Java perspective, the Open Associated Perspective dialog box is displayed where you can choose to go the Java perspective and edit code.

To import a Java RMI/JNI project from JBuilder

Build the RMI/JNI project in JBuilder. This expands any build macros that might be used as VM arguments, for example, similar to those used in the JBuilder Sample RMI project.
Follow the steps above for importing a JBuilder project.
Expand the project in the Package Explorer and select an RMI or JNI file.
Right-click the file and choose Properties to display the Properties for <filename> dialog box.
Choose the RMI/JNI Properties page to view property settings imported from JBuilder.

RMI options are set in the RMI Compiler Settings area of the dialog box.
JNI options are set in the JNI Compiler Settings area of the dialog box.

For more information, click F1.

To verify settings after importing a Java VisiBroker project from JBuilder

Open the VisiBroker page of the Preferences dialog box (WindowPreferencesVisiBroker).
Verify the directory where VisiBroker tools are installed. Typically, this is bin folder of your Borland Enterprise Server installation.
Click Apply and OK to save your settings.
Expand the project in the Package Explorer and select an IDL file or a Java interface file that will be translated from IDL, to IDL, or to IIOP.
Right-click the file and choose Properties to display the Properties for <filename> dialog box. Property settings have been imported from JBuilder.

For IDL to Java files, choose the VisiBroker IDL Properties page and verify options in the IDL2Java Settings area of the dialog box.
For Java to IDL files, choose the VisiBroker Java Properties page and verify options in the Java2IDL Settings area of the dialog box.
For Java to IIOP files, choose the VisiBroker Java Properties page and verify options in the Java2IIOP Settings area of the dialog box.

Building an Imported Project or Project Group

The build process uses a standard JDK compiler, not the JBuilder compiler, Borland Make for Java. Before you build your imported project, you can check compiler options on the Java Compiler page of the Properties dialog box.

The auto-build feature is on by default for new or imported projects. When auto-build is on, builds occur after every set of resource changes, so that .class files are always up-to-date. When auto-build is off, you can manually invoke builds. This is useful in cases where you are making changes to large sets of files. To toggle the auto-build setting, choose ProjectBuild Automatically or toggle the Build Automatically option on the Workspace page of the Preferences dialog box (WindowPreferencesGeneralWorkspace).

Note:	The build order is not displayed in the Package Explorer. The build order is displayed on the Build Order page of the Preferences dialog box (WindowPreferencesGeneralWorkspaceBuild Order).

To build an imported project

Turn off ProjectBuild Automatically to turn off auto-build.
Choose ProjectBuild Project to perform an incremental build on the selected project.
Choose ProjectBuild All to incrementally build all open projects.
Choose ProjectClean to delete all previous build output for the selected project. If auto-build is on, a full build is invoked.

To build an imported project group

Choose ProjectBuild Automatically to turn off auto-build.
Choose WindowPreferencesGeneralWorkspaceBuild Order to check the project build order. Uncheck the Use Default Build Order option and use the Up and Down buttons to rearrange the order of projects.
Choose ProjectBuild Working SetSelect Working Set to display the Select Working Set dialog box, where you select a working set for the project group or create a new one.

To create a working set, select the New button to display the New Working Set dialog box.
Select Java and click Next.
Enter a name in the Working Set Name field. Choose the projects to include in the working set from the Working Set Content list.
Click Finish to create the working set.

Choose ProjectBuild Working Set<Working Set Name> to build the project group.

To change the build order

Open the Build Order page of the Preferences dialog box (WindowPreferencesGeneralWorkspaceBuild Order).
Uncheck the Use Default Build Order option.
Select the project you want change the order for in the build. Use the Up and Down buttons to rearrange the build order.
Click the OK button to close the dialog box and save the new build order.

To change the output path

Open the Java Build Path page of the Properties dialog box (ProjectPropertiesJava Build Path).
Change the folder in the Default Output Folder field.
Click the OK button to close the dialog box and save the output path.

Running an Imported Project

The run configuration is automatically imported when you import a JBuilder project. The run configuration for each project in a project group is listed separately in the Run dialog box.

To run an imported project or project in a project group

Choose RunRun to open the Run dialog box.
Expand the node that matches the type of imported project in the Configurations list and choose the name of the configuration. Typically, the configuration name is the same as the project name.

Note:	You can examine any page of the Run dialog box and change settings.

Click the Run button to run the project.

Note:	If your project uses macros in the run VM arguments, you need to compile the project in JBuilder before importing it. Compilation expands the macros. If the project is not compiled, it will not run. An example of a JBuilder project that uses macros is the sample RMI project.

JBuilder 2006/Developer Studio 2006 Differences

The platform, modeled as a plug-in development environment, provides an end-to-end Java development platform. Plug-ins help create an adaptable and extensible system. The environment provides perspectives, editors, and views that can be added to, configured, or replaced through the implementation of plug-ins.

JBuilder 2007 adds views and editors to the existing Eclipse Java perspective, as well as providing a modeling perspective and an integrated set of development life-cycle management tools.

Perspectives

An JBuilder 2007 perspective provides a “flavor” for the development environment and defines the initial set and layout of views in the Workbench. Each perspective provides a set of functionality aimed at accomplishing a specific type of task. As you work in the Workbench, you will probably switch perspectives frequently. Perspectives are available from the WindowOpen Perspective menu command. You can set perspective preferences with the WindowPreferencesGeneralPerspectives command.

The Java perspective contains a code editor, a Package Explorer that is similar to the previous JBuilder Project pane, an Outline view that is similar to the previous JBuilder Structure pane, and a tabbed lower pane, for searching and error display, that is similar to the previous JBuilder Message pane. There is also a Debug perspective, a Java Browsing perspective, and a Java Type Hierarchy perspective that are similar to panes in the previous JBuilder IDEs.

Developer Studio 2006 adds views and editors to the Java perspective that are specific for developer needs, such as tools for editing code, viewing and editing requirements and change requests, profiling, and creating unit tests. Developer Studio 2006 also adds a Modeling perspective so that you can do most of these tasks while looking at a modeling view of your Java code. You can customize these perspectives with the WindowCustomize Perspective command.

Editors

Most perspectives contain one or more editors for editing code. JBuilder 2007 editors include a Java source code editor, a text editor, and a GUI visual editor. Developer Studio 2006 includes the modeling designer, requirements editor, and a change request editor. You can open as many editors as you wish, though only one editor is active at a time. The main menu and toolbar only contain items applicable to the active editor.

Views

Views provide alternative presentations of data. Views have unique context menus and may have unique toolbars. A view can be displayed on its own, or as a tabbed page in a multi-view presentation. Developer Studio 2006 provides multiple views, including the Modeling Perspective, the Requirements view, and the Profiling view.

Note:	Each view contains a toolbar with a drop-down menu icon.

Tips

There are many slight differences between the previous JBuilder IDEs and the user interface. The tips below can help you learn to navigate the Java perspective quickly. Note that these tips are not extensive or exhaustive, and cover just some of the frequently used features.

Feature	Tip
Editor	If a Java file has errors, a red “X” icon is displayed in the left margin of the editor. Hovering the mouse over the icon displays the error as a tooltip.
Editor	When the editor cannot display tabs for all open files due to space constraints, the number of files not displayed is shown on a toolbar button. Click the button to see a file list.
Editor	When using Code Assist (code insight in JBuilder 2006), a tooltip with available Javadoc is displayed.
Editor	The NavigateOpen Type Hierarchy command displays the type hierarchy of a specific source code element.
Editor	Hovering the mouse over a symbol displays Javadoc for that symbol, if available.
Editor	Clicking the mouse on an identifier marks all uses of that identifier in the current file. Locations where the identifier is used are marked in the gutter.
Editor	Typing a left-facing parenthesis, brace, or quote automatically adds the termination/closing mark.
Editor	Placing a caret in a symbol highlights all of its occurrences in the open file.
Editor	The gutter indicates lines of code that have changed.
Editor	Using the Navigate menu, you can search for references by a range of scopes, from the workspace to the current project to the current class hierarchy to just a selected group of files.
Editor	Previous searches are available from a drop-down menu in the Search view.
Editor	You can use the Java Search page of the Search dialog box (SearchJava) to search for the particular usage of a symbol.
Editor	Use the Change Method Signature refactoring to modify the signature of a method.
Editor	The Javadoc author name field is automatically filled in when creating a new class.
Editor	Optimize imports and code formatting can be applied to a group of files.
Editor	You can search for references on a selected import statement (SearchReferences).
Debugger	When a change is made, saved, and compiled during a debugging session, obsolete frames are automatically popped off the stack and the frame pointer is automatically set to the highest possible valid frame.
Debugger	To evaluate an expression, first execute the code (RunExecute), then display the results (RunDisplay).
Debugger	Only one JBuilder 2007 instance can be debugged at a time.
Debugger	Icons in the Variables view indicate the type of variable, for example, members or local variables.
Debugger	In the Debug perspective, right-click an application and choose Terminate All to remove all terminated launches.
Debugger	Breakpoints can be configured to stop when a condition changes, not just on a true/false condition. Breakpoints can also be configured to stop only in a particular thread.

Previous JBuilder/JBuilder 2007 Dialog Box Equivalents

The following tables show previous JBuilder IDE and JBuilder 2007 dialog box equivalents.

Project Properties dialog box

Previous JBuilder Versions	JBuilder 2007
Paths page (ProjectProject PropertiesPaths)	Java Build Path page (Project PropertiesJava Build Path)
JDK option on the Paths page (ProjectProject PropertiesPaths)	Libraries tab on the Java Build Path page (Project PropertiesJava Build Path)
Output path on the Paths page (ProjectProject PropertiesPaths)	Output Path option on the Java Build Path page (Project PropertiesJava Build Path)
Source tab on the Paths page (ProjectProject PropertiesPaths)	Source tab on the Java Build Path page (Project PropertiesJava Build Path)
Documentation tab on the Paths page (ProjectProject PropertiesPaths)	Javadoc Location page (Project PropertiesJava Build Path)
Required Libraries tab on the Paths page (ProjectProject PropertiesPaths)	Libraries tab on the Java Build Path page (Project PropertiesJava Build Path)
Compiler options on the Java page (ProjectProject PropertiesBuildJava)	Compiler page in the Preferences dialog box (WindowPreferencesJavaCompiler)

Tools menu

Previous JBuilder Versions	JBuilder 2007
Configure Libraries dialog box (ToolsConfigureLibraries)	User Libraries page in the Preferences dialog box (WindowPreferencesJavaBuild PathUser Libraries)
Configure JDKs dialog box (ToolsConfigureJDKs)	Installed JREs page in the Preferences dialog box (WindowPreferencesJavaInstalled JREs)
Browser page in the Preferences dialog box (ToolsPreferencesBrowser)	Web Browser page in the Preferences dialog box (WindowPreferencesGeneralWeb Browser)
Editor page in the Preferences dialog box (ToolsPreferencesEditor)	Web Browser page in the Preferences dialog box (WindowPreferencesJavaEditor)
Documentation tab on the Paths page (ProjectProject PropertiesPaths)	Javadoc Location page (Project PropertiesJava Build Path)
Required Libraries tab on the Paths page (ProjectProject PropertiesPaths)	Libraries tab on the Java Build Path page (Project PropertiesJava Build Path)

Previous JBuilder/JBuilder 2007 Menu Command and Keyboard Equivalents

The following tables show JBuilder and menu command and keyboard equivalents.

Note:	If no keyboard shortcut is listed, none is available.

File menu

Previous JBuilder Versions	JBuilder 2007
FileNew (Ctrl+N)	FileNew (Ctrl+N)
FileOpen File (Ctrl+O)	FileOpen File
FileClose (Ctrl+F4)	FileClose (Ctrl+F4)
FileClose All (Ctrl+Shift+F4)	FileClose All (Ctrl+Shift+F4)
FileSave (Ctrl+S)	FileSave (Ctrl+S)
FileSave All (Ctrl+Shift+S)	FileSave All (Ctrl+Shift+S)

Edit menu

Previous JBuilder Versions	JBuilder 2007
EditUndo (Ctrl+Z)	EditUndo (Ctrl+Z)
EditRedo (Ctrl+Shift+Z)	EditRedo (Ctrl+Y)
EditCut (Ctrl+X)	EditCut (Ctrl+X)
EditCopy (Ctrl+C)	EditCopy (Ctrl+C)
EditPaste (Ctrl+V)	EditPaste (Ctrl+V)
EditFormat All (Alt+Shift+K)	SourceFormat (Ctrl+Shift+F)
EditCode Insight (Ctrl+Space)	EditContent Assist (Ctrl+Space)
EditCode InsightParameterInsight (Ctrl+Shift+Space)	EditParameter Hints (Ctrl+Shift+Space)
EditCode InsightJavadoc QuickHelp (Ctrl+Q)	NavigateOpen External Javadoc (Shift+F2)
EditSelect All (Ctrl+A)	EditSelect All (Ctrl+A)

Search menu

Previous JBuilder Versions	JBuilder 2007
SearchFind (Ctrl+F)	EditFind/Replace (Ctrl+F)
SearchFind In Path (Ctrl+P)	SearchSearchJava Search (Ctrl+H)
SearchReplace (Ctrl+R)	EditFind/Replace (Ctrl+F)
SearchSearch Again (F3)	EditFind Next (Ctrl+K)
SearchSearch Incremental (Ctrl+E)	EditIncremental Find (Ctrl+J)
SearchGo To Line (Ctrl+G)	NavigateGo To Line (Ctrl+L)
SearchGo To Class Member (Ctrl+Shift+G)	Select class member, then NavigateGo ToNext Member (Ctrl+Shift+Up)
SearchGo To Previous Method	Select method, then NavigateGo ToPrevious Member (Ctrl+Shift+Down)
SearchGo To Next Method	Select method, then NavigateGo ToPrevious Member (Ctrl+Shift+Down)
SearchFind Classes (Ctrl+Minus)	NavigateOpen Type (Ctrl+Shift+T)
SearchFind Definition (Ctrl+Enter)	NavigateOpen Declaration (F3)
SearchFind ReferencesJavadoc QuickHelp (Ctrl+Shift+Enter)	SearchReferencesProject
SearchFind Referring Classes	SearchReferencesHierarchy

Refactor menu

Previous JBuilder Versions	JBuilder 2007
RefactorOptimize Imports (Ctrl+I)	SourceOrganize Imports (Ctrl+I)
RefactorRename	RefactorRename (Alt+Shift+R)
RefactorMove	RefactorMove (Alt+Shift+V)
RefactorInline	RefactorInline (Ctrl+Shift+I)
RefactorChange Parameters (Ctrl+S)	RefactorChange Method Signature (Alt+Shift+C)
RefactorExtract Interface From	RefactorExtract Interface
RefactorExtract Method (Ctrl+Shift+E)	RefactorExtract Method (Alt+Shift+M)
RefactorSurround with Try/Catch (Ctrl+Shift+C)	SourceSurround with Try/Catch Block

Project menu

Previous JBuilder Versions	JBuilder 2007
ProjectMake Project (Ctrl+F9)	ProjectBuild All (Ctrl+B)
ProjectRebuild Project	ProjectBuild All (Ctrl+B)
ProjectMake <File> (Ctrl+Shift+F9)	ProjectBuild All (Ctrl+B)
ProjectRebuild <File>	ProjectBuild All (Ctrl+B)
ProjectMake Project Group	ProjectBuild Working Set

Project Properties

Once a project has been imported into the workspace, you can right click the project node and choose Properties to view project properties, including the build and output paths, library settings, and compiler options.

Paths

When a JBuilder Java project is imported, without doing a checkout, the project's source path remains in the/src folder in the project's original location. If you check out a project from version control, all source files are placed in the workspace and the source path is relative to the workspace.

The previous JBuilder classpath is analogous to the Java build path in JBuilder 2007. The build path is displayed on the Java Build Path page of the Properties dialog box. By default, the output path is the /bin folder in the workspace, not the /classes folder, as in JBuilder You can change the path on the Java Build Path page of the Properties dialog box.

Note:	The Package Explorer does not display projects in their build order. To see the build order for multiple projects, open the Build Order page of the Preferences dialog box (WindowPreferencesGeneralWorkspaceBuild Order).

Libraries

Libraries are saved to the workspace. Libraries that are required for the project are displayed on the Libraries tab of the Java Build Path page in the Properties dialog box.

The project import compares JDK version labels and translates the project JDK to the JRE in the eclipse/jre folder of your installation. Subsequent imports of additional projects search for a JDK with the same version as an already-imported JDK. If one exists, that JDK is used, instead of creating multiple, identical JREs.

Note:	The project import brings in both project libraries and libraries that those libraries require.

Compiler Options

Imported compiler options are display on the Java Compiler page of the Properties dialog box. If the compiler compliance level for the workspace is different from that of the imported project, the import makes a project-specific override. For VisiBroker projects, the Compiler Compliance Level on the Java Compiler page needs to be set to 1.4 or 1.3.

JBuilder-Specific Properties Pages

Property pages are supplied for JBuilder specific properties, such as VisiBroker or RMI/JNI projects. To view these property pages, right-click an IDL or Java interface file after the project import. Press F1 on these pages for more information.

Project Nodes

A JBuilder project can have multiple nodes, including J2EE nodes, archive nodes, Javadoc nodes, a Generated Source node, a build node, and so on. Not all nodes can be imported into the workspace. The following nodes are not imported:

Archive node
Javadoc node
Generated Source node

If your project has an Archive node, you can recreate the archive with the FileExportArchive File command. You can regenerate Javadoc with the FileExportJavadoc command.

On project import, auto-generated source files are not imported or automatically regenerated. However, when you build your imported project, the generated source files are created in the /Generated Source folder of the workspace. The /Generated Source folder is added to the source path on the Source tab of the Java Build Path page of the Properties dialog box (ProjectPropertiesJava Build Path). In JBuilder 2007, auto-generated files are referred to as Derived files. The Derived setting is on the Info page of the Properties dialog box (PropertiesInfo from the context menu in the Package Explorer with the folder selected).

Run Configuration

When a Java project from JBuilder is imported into the workspace, the run configuration is also imported. This configuration includes run and debug settings. You can view the run configuration in the Run dialog box (RunRun). Configurations are sorted by type in the tree on left. In JBuilder 2007, a run configuration is known as a launch configuration.

Source Control

JBuilder projects under source control can be checked out to the workspace. When you check out directly from the repository into the workspace, an JBuilder 2007 project is created without any of the project elements that are not files. The check out pulls all source files into the workspace.

JBuilder projects can be checked out from the following source control systems:

Subversion
ClearCase
CVS
StarTeam
Visual SourceSafe

Note:	Subversion is the only source code control system supported by Team Assist.

Warning:	CVS and Subversion projects that are checked into a local repository cannot be checked out.

If the project is under source control, the Enable VCS Plugin option on the Import JBuilder Project wizard or the Import JBuilder Project Group wizard is available. If the project is under source control and you do not select this option, the JBuilder project is imported from its original location. If some, but not all projects in a project group are under source control, the option only applies to the projects under source control.

Note:	Before the check out, you may be required to log into the repository or synchronize the local version with the version in the repository.

Copyright © 2006 Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners..

JBuilder 2007 Migration Guide