CLI Project Path Reset

If the source code path during export is different from the source code path when importing, an error occurs as shown below.

In this case, you can specify a new path through mapping while importing the project in the CLI. The mapping method is as follows.

1. When you export a project, a PathMappingFile.csv file will be created in the specified directory.
2. Edit the PathMappingFile.csv file.
   • Old Path: This is the path specified during the project export process.
   • New Path: This is the path to be used during the import process.
   • status: Indicates the status of the path.
     • If the file path is normal: “OK”
     • If the existing [Old Path] is invalid and no [New Path] has been entered: “The old path is invalid. Please enter a new path.”
     • In case the entered [New Path] does not exist: “The new path you entered is not valid. Please check the new path.”
     • In cases where source code is included in the export : “This project contains source files. Do not enter new path If you import with source files.”
   1. If the paths on the exporting PC and the importing PC are the same, leave the [New Path] column empty.
      
   2. If the code paths on the exporting PC and the importing PC are different, add the path to be used on the importing PC in the [New Path] column.
      
3. Apply the PathMappingFile.csv using the —mapping-file option when importing the project.
   • Example : -e -w "%workSpacePath%" --import -O "--path '%Project path%' --mapping-file '%PathMappingFile.csv path% --include-tch'"
     
4. After the command is executed, the results for each path can be checked in the PathMappingFile.csv file.