D
dbeavon
Guest
I am in favor of having more tooling. I am always surprised by how much custom tooling an OpenEdge developer needs to create themselves, because nothing is provided by Progress. This example (being unable to compile projects from the command line) is just one example of many. I think PCT is great, because it is built in the community. I suspect it would be hard for Progress itself to keep up and produce every possible tool that was needed in the OpenEdge development community. What makes me grumpy is that Progress hasn't yet moved to make a few things open source, and hasn't started taking pull requests. For example, this .propath file issue shouldn't be such a hang-up. I suspect there could be a path hint of some kind that points to the location of other projects that are used as dependencies. Back on the topic of the Java API for parsing the .propath into a PROPATH... Is there someone who can point me to where that stuff sits in a PDSOE installation so that we can inspect it? All my inter-project references are easy to find, so that will not be an issue on my end.
Continue reading...
Continue reading...