-
Notifications
You must be signed in to change notification settings - Fork 64
Gilles QUERRET edited this page May 3, 2015
·
9 revisions
This page summarize frequently asked questions (and answers) around build automation with Ant, PCT and OpenEdge.
- Please use the Issues page on GitHub.
- Always include the version number of PCT and OpenEdge ; you can easily get this information by including the following statements in your build.xml :
<PCTVersion />
<ProgressVersion dlcHome="${DLC}" fullVersion="dlc.version.full" />
<echo message="${dlc.version.full}" />
Which will give you :
[PCTVersion] PCT Version : jenkins-Dev1-PCT-376
[echo] OpenEdge Release 11.5 as of Fri Dec 5 19:02:15 EST 2014
- Upgrade to the latest version of PCT if possible
- Include a verbose log of your problem, by using
ant -v
- Include if possible a PCT verbose log of your problem, by adding verbose="true" in your PCTRun or PCTCompile statement
- If you have a problem with PCTCompileExt, first verify that PCTCompile works correctly.
- If you want a problem to be fixed in a short amount of time, include a test case to reproduce the problem. The easier it will be for me to reproduce the problem, the faster the fix will come
- If you know how to fix a problem, please create a pull request
- QuickStart
- Changelog
- InstallDocumentation
- FAQ
-
Tasks
- PCT
- DlcHome
- PCTRun
- PCTDynRun
- PCTCompile
- PCTWSComp
- PCTCreateDatabase
- Sports2000
- Sports2020
- PCTDumpSchema
- PCTDumpSequences
- PCTLoadSchema
- PCTIncrementalDump
- PCTBinaryDump
- PCTBinaryLoad
- PCTDumpData
- PCTLoadData
- PCTSchemaDoc
- PCTLibrary
- PCTProxygen
- PCTXCode
- ProgressVersion
- PCTVersion
- ClassDocumentation
- HtmlDocumentation
- XMLDocumentation
- JsonDocumentation
- ABLDuck
- OEUnit
- ABLUnit
- RestGen
- AssemblyCatalog
- Types