Hi,
is there a good reason or is it a bug that PDSOE does only support the two (OpenEdge provided) path variables @{APP} and @{DB} for the propath.
The Eclipse default ones (defined in the Workspace preferences on the General -> Workspace -> Linked Resources so not seem to work. According to the Eclipse docs those have to be references using the $ sign. When using them in the propath of an OpenEdge project, they do not seem to get replaced with the actual value.
For me that sounds like a bug, right?
Cheers,
Mike
Minor addition: You can use the path variables for referencing linked folders which can be used in the propath.
But that's way to complicated. There must by a way to have more than just the two OpenEdge supported path varaibles @{APP} and @{DB}
I had a bash at this with tech support a few months back, in my case it was using a derivative of @{workspace_loc} in the build location and in the run configurations. This is called 'not yet implemented functionality', the work-around being hard-coded paths. Linked resources looked promising at the time - they could be added to the propath - but were subsequently ignored when passed to the compile session.
(C) 2006-2008 in the header of _debuglauncher.p doesn't really give much hope either - although in this case the implementation needs to be done in the java side.
Hi Mike,
We have provided this functionality in PDSOE 11.6. User can now define their own custom path variables at project and workspace level. These variables can be used in the project properties and also workspace preference pages.
Hi Mike,
We have provided this functionality in PDSOE 11.6. User can now define their own custom path variables at project and workspace level. These variables can be used in the project properties and also workspace preference pages.
Flag this post as spam/abuse.