Among the notes on migration of workspace and projects, the following can be automatically updated using workbench commands:
To convert these settings automatically, follow the procedure below.
To use workspace or project of previous version in the workbench of current version, follow the procedure described in "Migration procedure"
Select [Project] > [Update Workspace/Projects of Previous Version] from the menu bar.
The [Update Workspace/Projects of Previous Version] dialog box is displayed. On the left side of the dialog box, workspaces and projects requiring settings updates are displayed. Select the items to be updated, and then click [OK].
Workspace and project settings are updated. In the Console view, the status of the update is displayed. Make sure that the update has been performed successfully.
Note
This command does not update closed projects, so open the projects to be updated before using it.
If an automatic build is performed after the command, then the project may be displayed with an error mark in the Package Explorer view, even though the classpath is successfully set. In this case, clear the error mark by cleaning the project first and performing build again.
Projects that meet all the following requirements may also be displayed with an error showing "Missing builder(com.fujitsu.apworks.apdesinger.java.packagerbuilder)" in the builders under the projects' properties, even though the projects have been automatically updated. In this case, please perform an automatic update once again.
Resources are developed in the V9 workbench or V10-compatible workbench.
Builders of the project are set as [JAR Packager Builder].
Build path of the project is set as [Interstage J2EE] library.
Besides, problems such as builder mistakes will not occur, even though there is an error showing "Missing builder(com.fujitsu.apworks.apdesinger.java.packagerbuilder)".
