Search Gradle plugins

progress.openedge.abl

Owner: Progress Software

Create a Continuous Integration pipeline for your OpenEdge applications using OpenEdge DevOps Framework.

https://docs.progress.com/bundle/openedge-devops-framework

Version 2.0.0

Created 12 January 2022.

1. The minimum supported Gradle version is now 7.3.3. In Gradle version 7.3.3 the log4j vulnerabilities are addressed (https://docs.gradle.org/7.3.3/release-notes.html).
2. OEDF can now get PCT directly from maven as an alternative to the default behavior of using the PCT library shipped with OpenEdge by setting the property PCT_VERSION={version_number}. For example, PCT_VERSION=221. This property can be set as a system property (using -D option on the command line), as a Gradle property (in 'gradle.properties' file) or as an environment variable.
3. The file 'project-result.json' contains the list of errors and warnings upon compilation and gets generated when the compileOptions.outputType="json" is specified. In the file the keys 'ttProjectErrors' and 'ttProjectWarnings' are replaced by 'errors' and 'warnings', respectively.
4. The build script used with OEDF 1.0.1 can be used with OEDF 2.0.0, however the gradle version must be updated with OEDF 2.0.0.
Other versions 

Using the plugins DSL:

plugins {
  id "progress.openedge.abl" version "2.0.0"
}

Using legacy plugin application:

buildscript {
  repositories {
    maven {
      url "https://plugins.gradle.org/m2/"
    }
  }
  dependencies {
    classpath "gradle.plugin.progress.openedge:abl:2.0.0"
  }
}

apply plugin: "progress.openedge.abl"

Using the plugins DSL:

plugins {
  id("progress.openedge.abl") version "2.0.0"
}

Using legacy plugin application:

buildscript {
  repositories {
    maven {
      url = uri("https://plugins.gradle.org/m2/")
    }
  }
  dependencies {
    classpath("gradle.plugin.progress.openedge:abl:2.0.0")
  }
}

apply(plugin = "progress.openedge.abl")

Learn how to apply plugins to subprojects