To import Java source code files, bytecode files, and resource files from the file system to the Workspace:
Note: Because the Import SmartGuide can look into Jar and zip files, you do not need to unzip them before importing files that are in them.
Imported Java code is compiled and unresolved problems that are introduced are added to the All Problems page. Open editions of the classes and interfaces are created in the VisualAge for Java repository, and added to your workspace. If you select to automatically version program elements, then they will be versioned after importing.
Resource files (any file imported that is not a .java or .class file) are copied into the local resources directory for the project.
If you import only bytecode (compiled Java code in .class files), and not source code,
for a class or interface, then you will not be able to edit the source in the workspace.
These classes are indicated in the Workbench and other browser lists by the bytecode file
symbol .
If the containing
package or project in your VisualAge for Java workspace has been versioned, then a scratch
edition of the package or project will be created. To prevent this, create an open edition
of each project or package before importing.
Exporting Code
Finding and Fixing Problems
Including Resource Files in a Project