Abstract: Learn how to import your previous JBuilder projects into JBuilder 2007
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.
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:
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.
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.
Some project properties are not supported in or are translated to the equivalent on import. The following table illustrates those items:
/Additional Settings Folder
Not imported; no equivalent.
Not imported. Regenerate with FileExportJavadoc.
Left in code.
Before importing JBuilder J2EE or VisiBroker project, you need to configure application server and VisiBroker locations.
To set properties for importing J2EE projects
To set properties for JBuilder VisiBroker project imports
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
You can also choose FileImport...Legacy JBuilderJava Project(s) from Existing JBuilder Project.
CVS and Subversion projects that are checked into a local repository cannot be checked out.
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.
To import a Java J2EE project from JBuilder:
You can also choose FileImport...Legacy JBuilderJava EE Project(s) from Existing JBuilder Project.
To import a Java RMI/JNI project from JBuilder
For more information, click F1.
To verify settings after importing a Java VisiBroker project from JBuilder
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).
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
To build an imported project group
To change the build order
To change the output path
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
You can examine any page of the Run dialog box and change settings.
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.
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.
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.
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 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.
Each view contains a toolbar with a drop-down menu icon.
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.
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.
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.
When using Code Assist (code insight in JBuilder 2006), a tooltip with available Javadoc is displayed.
The NavigateOpen Type Hierarchy command displays the type hierarchy of a specific source code element.
Hovering the mouse over a symbol displays Javadoc for that symbol, if available.
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.
Typing a left-facing parenthesis, brace, or quote automatically adds the termination/closing mark.
Placing a caret in a symbol highlights all of its occurrences in the open file.
The gutter indicates lines of code that have changed.
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.
Previous searches are available from a drop-down menu in the Search view.
You can use the Java Search page of the Search dialog box (SearchJava) to search for the particular usage of a symbol.
Use the Change Method Signature refactoring to modify the signature of a method.
The Javadoc author name field is automatically filled in when creating a new class.
Optimize imports and code formatting can be applied to a group of files.
You can search for references on a selected import statement (SearchReferences).
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.
To evaluate an expression, first execute the code (RunExecute), then display the results (RunDisplay).
Only one JBuilder 2007 instance can be debugged at a time.
Icons in the Variables view indicate the type of variable, for example, members or local variables.
In the Debug perspective, right-click an application and choose Terminate All to remove all terminated launches.
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.
The following tables show previous JBuilder IDE and JBuilder 2007 dialog box equivalents.
Project Properties dialog box
Previous JBuilder Versions
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)
Compiler options on the Java page (ProjectProject PropertiesBuildJava)
Compiler page in the Preferences dialog box (WindowPreferencesJavaCompiler)
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)
The following tables show JBuilder and menu command and keyboard equivalents.
If no keyboard shortcut is listed, none is available.
FileOpen File (Ctrl+O)
FileClose All (Ctrl+Shift+F4)
FileSave All (Ctrl+Shift+S)
EditFormat All (Alt+Shift+K)
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)
SearchFind In Path (Ctrl+P)
SearchSearchJava Search (Ctrl+H)
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
SearchFind Classes (Ctrl+Minus)
NavigateOpen Type (Ctrl+Shift+T)
SearchFind Definition (Ctrl+Enter)
NavigateOpen Declaration (F3)
SearchFind ReferencesJavadoc QuickHelp (Ctrl+Shift+Enter)
SearchFind Referring Classes
RefactorOptimize Imports (Ctrl+I)
SourceOrganize Imports (Ctrl+I)
RefactorChange Parameters (Ctrl+S)
RefactorChange Method Signature (Alt+Shift+C)
RefactorExtract Interface From
RefactorExtract Method (Ctrl+Shift+E)
RefactorExtract Method (Alt+Shift+M)
RefactorSurround with Try/Catch (Ctrl+Shift+C)
SourceSurround with Try/Catch Block
ProjectMake Project (Ctrl+F9)
ProjectBuild All (Ctrl+B)
ProjectMake <File> (Ctrl+Shift+F9)
ProjectMake Project Group
ProjectBuild Working Set
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.
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.
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 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.
The project import brings in both project libraries and libraries that those libraries require.
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.
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.
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:
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).
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.
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 is the only source code control system supported by Team Assist.
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.
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..
Server Response from: ETNASC01