R
Ravi Sankar
Guest
Gradle is a build automation tool like ANT. It uses Groovy or Kotlin as the language for writing the build scripts. So, unlike ANT, which uses XML to write logic like copy files, change properties, update configuration etc, you can use make use of a full fledged programming language to write logic. Gradle also has other benefits like repository integration, dependency management etc. Gradle has a notion of plugins (much like eclipse) to add additional features to the build process. The gradle plugin we are planning to ship with 12.2 will not be open source. It is not an eclipse/PDSOE plugin. We want the customers to use this in the CI environment. Eventually, PDSOE also will use the same Gradle plugin for compiling source code. In 12.2, PDSOE will make use of the same builder as it used in 12.1 & before releases. However, in 12.2, PDSOE will read the build configuration from a configuration file (which is separate from .propath) and this configuration file along with .propath will be understood by PDSOE and the Gradle plugin in a similar way. We will post a sprint demo recording in CVP so that you can get some better idea. With respect to how the PASOE projects should be compiled and packaged, Peter Judge did a talk in last year PUG/Next. We are in the process of implementing these changes both by PASOE to understand these packaging structures and deploy them and PDSOE/OEM to provide tooling support. Our vision is that the build/packaging should be run in the same way in dev/CI environments. These changes are being done in 12.x releases only. For 11.7.x, for compilation (and packaging as PL), outside PDSOE, PCT can be used. PDSOE also exposed couple of ANT tasks which can be used for packaging outside PDSOE. However, the packaging support is only for Web applications and custom scripts should be written for packaging ABL applications.
Continue reading...
Continue reading...