Kbase P131350: After upgrading to 10.1C r-code is saved into common workspace for linked resources
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/2/2008 |
|
Status: Verified
SYMPTOM(s):
After upgrading to 10.1C r-code is saved into common workspace for linked resources
r-code is not in same directory as source code
No build destination is specified
FACT(s) (Environment):
Windows 32 Intel
OpenEdge 10.1C
CAUSE:
Bug# OE00168552
CAUSE:
This is expected behavior; sort of...
When no build destination is specified Architect places generated r-code in the project directory plus the relative path by which the program is addressed. Typically this amounts to the r-code ending up in the same directory as the source code.
When linked project directories are used to store the source code however, the r-code is generated underneath the physical project directory, which is local to the workspace. Ideally the project directory would be a logical directory "only" and the r-code would end up in the same location as the source code but there are limitations in the ABL and the Eclipse model which make this difficult to achieve.
Progress development is aware of this limitation and will attempt to address it in some future release of the product.
FIX:
The recommendation is to use build destinations to be sure you know where your r-code will be placed when it is generated. This allows one to specify any physical path to which the r-code will be generated.