A Packager project consists of a project configuration and a set of files, which together fully determine the installation. A project defines:
This information is stored in a Packager project file that you create as described later in this chapter. Packager project files have extensions “.eit” (for new installations) and “.eiu” (for updates).
You may create a new Packager project by clicking the New button on the Packager splash screen or by selecting the File/New menu item. This brings up the New page. If there is already an opened project, you are prompted to save it first. If there is already an opened project, Packager will prompt you to save it first.
You may open a previously created project right on Packager startup by clicking the Open button on the Packager splash screen or later by selecting the File/Open menu item. A conventional file dialog will appear; use it to browse for the Packager project file you want to open or select the desired project in the File name combo box.
Later you may quickly open an existing project using the File/Reopen menu item.
You can save a project by selecting the File/Save item from the main menu. When you save a just created project for the first time, a conventional file dialog is displayed; use it to specify the desired pathname for your project file. The default extension “.eit” is added to the file name automatically.
You can save the current project with a different name or in another directory by selecting the File/Save As item from the main menu. A conventional file dialog is displayed; use it to specify a new directory and/or a new name for your project file.
In some cases, you may need to create the resulting package in an environment different from where the project was created, for example, on another machine or on the same computer with the placement of package files changed. In such scenario, it would be reasonable to reuse the existing project file rather than to create a new project from scratch. Packager can help you update the existing project so that all settings and properties you specified in it are retained.
Suppose that the package files were copied to (or built in) the new environment. Ideal case for packaging would be just copying the project file (.eit) to the new location and rebuilding the package in the batch mode. The problem, however, is that placement of the package files in the file system may be changed during relocation so the existing project cannot be reused directly.
Packager automatically detects if the project was relocated, and attempts to find all package files, using paths relative to the new placement of the project file. If some of the files are not found this way, Packager lets you either supply the files, or remove them from the project.
The following procedure helps you easily relocate an existing Packager project.
), fix them as follows:
Enable the Show full path checkbox on the bottom pane to see where Packager expects to find the missing files. Then, either copy or move the files to the appropriate location or remove them from the project and add such files again from their present locations using the Filechooser pane on the right. Note that in the latter case file-specific settings, such as system properties (see ???) will be lost.