Handling of Complete vs Partial Paths in the Import Path-Matching Process

When the project import process considers whether to add a file to inventory or mark it as reviewed, the file-matching criteria can mandate that the path of the file match between the import data file and the target project. For example, if the file-matching criteria requires that the complete paths of files match, the file /ePortal-1.3/src/gettext.c—the only file belonging to “InventoryItem 1.0 (License1)” in the import data file—is considered to be a different file from /ePortal-2.0/src/gettext.c in the target project. As a result, ePortal-2.0/src/gettext.c cannot be associated with “InventoryItem 1.0 (License1)”; and, if the createEmptyInventory value is false, “InventoryItem 1.0 (License1)” is not created in the target project since it has no associated file. Additionally, ePortal-2.0/src/gettext.c will not be marked as reviewed in the target project.

In order for a file in the target project to be treated as identical to a file in the data file, the paths for the two files must match in both locations. To accomplish this, you can use “partial path” and its directory depth as the file-matching criteria. In the case above, you would ensure that the file paths match by selecting “partial path” and setting its directory depth to 1 (one directory above the file name). In this way, the import is matching only the partial path /src/gettect.c for both files. Alternatively, you can manually manipulate paths in the import data file to match those in the target project, but you are strongly recommended to apply the “partial path” and directory depth criteria instead.