Importing and Exporting a Project in RBD v8.0.1
alicec 060000B6VQ Visits (5592)
Starting in Rational Business Developer version 8.0.1, the Project Interchange Format (PIF) import/export wizard has been replaced by existing Eclipse Import and Export wizards. You can use these wizards to export EGL projects to an archive file and import EGL projects from an existing PIF or archive file.
To export an EGL project, use the Export Archive File wizard as follows:
In this example, myProject is exported to d:\t
To import an EGL project into your workspace from an existing PIF or archive file, do the following:
In this example, myProject in d:\t
Managing Empty Java Source Folders
EGL projects can contain two types of Java source folders.
Due to an existing Eclipse bug (Bugzilla #278402 - [Import/Export] Export project does not export empty folders), empty folders in a project are not exported. If a Java source folder in an EGL project is empty (i.e. not exported), the following errors will occur when someone imports the project:
These problems occur because a Java source folder in the Java build path doesn't exist in the project. (To check a project's Java build path, right click on the project and select Properties > Java Build Path. Click the Source tab to see the source folders.)
The Eclipse bug is being worked on, but until it is fixed, you can either 1) remove or 2) populate empty source folders on the project's Java build path before exporting an EGL project:
If you remove EGLGen/JavaSource but it is later needed to hold generated Java, RBD will create a new one.
This will cause the folder to be exported, thus preventing errors after import.
After importing a project with errors, you can either 1) remove the missing source folder from the project’s Java build path or 2) create the folder in the project:
If you prefer, you can change your Java preferences to treat Java build path problems as warnings instead of errors. To do this: