Hi,
We are working with the OpenEdge Architect in 10.2 SP 7 HF 10 on Windows 7.
We have a "default" application that, depending on the propath, works for several customers. It is actually the order of the propath entries that vary in the propath for each customer. This means that for customer 1 the propath can be c:\myapp\prg,c:\myapp\dis,c:\myapp\crm and for customer 2 the propath can be c:\myapp\dis,c:\myapp\prg,c:\myapp\crm. I know this is not the way it should be, but it is the situation we are coping with (application is 20years+)...
The default location of the application is c:\myapp, all entries in the propath are subdirectories of that folder. In the OpenEdge Architect we want to see the content of the c:\myapp directory (and his subdirectories)
Now, we want to start using the OpenEdge Architect for this application (multiple developers). We thought that we could define 1 project for each propath (so 1 project for each customer) but we fail setting this up in the OpenEdge Architect.
Creating a project in the c:\myapp directory is not an option because the .propath-file is normally created in the application directory (i.c. c:\myapp) and that is not what we want because of the different propaths for each project.
So we tried to set the default location of the project to another folder (c:\myprojects\customer1) so the project files will be generated in this folder. Propath is set correctly but the content of the c:\myapp directory are not shown in the project explorer view. One of the many things we've already tried is to change the @{app} variable to c:\myapp but that made no difference.
What are we missing or is what we want to establish not possible?
Kind regards,
Peggy
Several of the source control plugins for eclipse have problems with linked resources (clearcase plugins throw NPE all over the place) or simply don't support them (SVN at one point didn't work at all...not sure if it has been fixed). Your mileage will vary.
What it seems you need is is separate .r files for customers based on which include file is in the PROPATH. PDSOE has no way to generate multiple r files for a single .p. It runs a single code path per .p, and generates one only one .r per .p. The only way around this is to turn off save of r-code on the compile (there is option in project preferences to do this) and use separate run configurations each with a separate PROPATH and let the AVM compile on the fly. This is imperfect as you won't get a compile for each customer, but only the one mapped for the current PROPATH.
I believe RoundTable can handle something like this with separate branches for different customers and it takes care of the compile and run when the include file changes.
I would suggest you review your use of include files and make some effort to get away from this model.
Working with the c:\myapp directory as linked folder is exactly what we needed! It was the magical trick we were missing :-).
Tnx for all the suggestions!
Hi,
We are working with the OpenEdge Architect in 10.2 SP 7 HF 10 on Windows 7.
We have a "default" application that, depending on the propath, works for several customers. It is actually the order of the propath entries that vary in the propath for each customer. This means that for customer 1 the propath can be c:\myapp\prg,c:\myapp\dis,c:\myapp\crm
and for customer 2 the propath can be c:\myapp\dis,c:\myapp\prg,c:\myapp\crm. I know this is not the way it should be, but it is the situation we are coping with (application is 20years+)...
The default location of the application is c:\myapp, all entries in the propath are subdirectories of that folder. In the OpenEdge Architect we want to see the content of the c:\myapp directory (and his subdirectories)
Now, we want to start using the OpenEdge Architect for this application (multiple developers). We thought that we could define 1 project for each propath (so 1 project for each customer) but we fail setting this up in the OpenEdge Architect.
Creating a project in the c:\myapp directory is not an option because the .propath-file is normally created in the application directory (i.c. c:\myapp) and that is not what we want because of the different propaths for each project.
So we tried to set the default location of the project to another folder (c:\myprojects\customer1) so the project files will be generated in this folder. Propath is set correctly but the content of the c:\myapp directory are not shown in the project explorer
view. One of the many things we've already tried is to change the @{app} variable to c:\myapp but that made no difference.
What are we missing or is what we want to establish not possible?
Kind regards,
Peggy
Flag this post as spam/abuse.
Thread created by peggycoleHi,
We are working with the OpenEdge Architect in 10.2 SP 7 HF 10 on Windows 7.
We have a "default" application that, depending on the propath, works for several customers. It is actually the order of the propath entries that vary in the propath for each customer. This means that for customer 1 the propath can be c:\myapp\prg,c:\myapp\dis,c:\myapp\crm and for customer 2 the propath can be c:\myapp\dis,c:\myapp\prg,c:\myapp\crm. I know this is not the way it should be, but it is the situation we are coping with (application is 20years+)...
The default location of the application is c:\myapp, all entries in the propath are subdirectories of that folder. In the OpenEdge Architect we want to see the content of the c:\myapp directory (and his subdirectories)
Now, we want to start using the OpenEdge Architect for this application (multiple developers). We thought that we could define 1 project for each propath (so 1 project for each customer) but we fail setting this up in the OpenEdge Architect.
Creating a project in the c:\myapp directory is not an option because the .propath-file is normally created in the application directory (i.c. c:\myapp) and that is not what we want because of the different propaths for each project.
So we tried to set the default location of the project to another folder (c:\myprojects\customer1) so the project files will be generated in this folder. Propath is set correctly but the content of the c:\myapp directory are not shown in the project explorer view. One of the many things we've already tried is to change the @{app} variable to c:\myapp but that made no difference.
What are we missing or is what we want to establish not possible?
Kind regards,
PeggyStop receiving emails on this subject.Flag this post as spam/abuse.
I need it for running
I'll try Tim's suggestion tomorrow, sounds like my solution :-)
It is not for running but for developing. Some includes exists in different sub folders (= customer folders) and depending on the propath the compiler take other includes. So we need different projects for the same main folder...
I tried Tim's suggestion but in the customer-project the content op c:\myapp is not shown. Do we miss something here?
Is it possible to have a project where the project-property-files (.propath and others) are in a different folder then the folder where the application is in?
Reply by peggycoleIt is not for running but for developing. Some includes exists in different sub folders (= customer folders) and depending on the propath the compiler take other includes. So we need different projects for the same main folder...
I tried Tim's suggestion but in the customer-project the content op c:\myapp is not shown. Do we miss something here?
Is it possible to have a project where the project-property-files (.propath and others) are in a different folder then the folder where the application is in?
Stop receiving emails on this subject.Flag this post as spam/abuse.
You can try using linked folders and files. Keep all project files and folders in one place. Create project in workspace location only and under project create linked folder to the source. This way all files will be listed in project explorer. Same way you can have linked folders in other project also.
Please try and let us know if linked folders and files solves your problem.
Thanks,
Swathi.
I was going to suggest linked folders, but i've had some awful performance issues surrounding this in the past.
Several of the source control plugins for eclipse have problems with linked resources (clearcase plugins throw NPE all over the place) or simply don't support them (SVN at one point didn't work at all...not sure if it has been fixed). Your mileage will vary.
What it seems you need is is separate .r files for customers based on which include file is in the PROPATH. PDSOE has no way to generate multiple r files for a single .p. It runs a single code path per .p, and generates one only one .r per .p. The only way around this is to turn off save of r-code on the compile (there is option in project preferences to do this) and use separate run configurations each with a separate PROPATH and let the AVM compile on the fly. This is imperfect as you won't get a compile for each customer, but only the one mapped for the current PROPATH.
I believe RoundTable can handle something like this with separate branches for different customers and it takes care of the compile and run when the include file changes.
I would suggest you review your use of include files and make some effort to get away from this model.
Working with the c:\myapp directory as linked folder is exactly what we needed! It was the magical trick we were missing :-).
Tnx for all the suggestions!