Kbase P140179: Is the project.xml updated when importing shared project to a different workspace?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/22/2009 |
|
Status: Unverified
GOAL:
Is the path of -assemblies startup parameter modified when importing project to different workspace?
GOAL:
Is the project.xml updated when importing shared project to a different workspace?
GOAL:
Is the project.xml modified when importing project to another workspace?
GOAL:
Is the path of the -assemblies startup parameter updated when importing projecto to another workspace?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
The export/import for the project does not change the value of the -assemblies parameter, therefore the project.xml is not updated.
This happens in case we want to actually use -assemblies directory specified in the other workspace.
A recommendable approach is to use the same assemblies directory for all the workspaces, so that when importing/exporting projects, the project.xml always refers to the same directory.
The -assemblies directory can use a path relative to the working directory (which is the project directory by default).
For example: -assemblies ../Assemblies.