Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 4.x

  • 5.x

  • 18.x

  • 19.1

  • 19.2

  • 20.1

  • 20.2

  • 22.x

  • 23.x

Recommended SQLcl Versions

  • Use

...

  • the SQLcl version

...

  • recommended by Oracle.

  • 21

    • This requires Java 8 or 11.

  • 22,23+

    • This requires Java 11.

  • Version Note that newer versions require Java 11. Make a second localhost or remote Endpoint which points to a second Java Home.

  • SQLcl version 23.2.0.178.1027 does not work. Upgrade to the later at least version 23.3 if you get a strange null pointer while attempting to deploy with an earlier 22 or 23 version.

  • If you use Autonomous Database, you must use SQLcl 23.3+ and Java 11.

Key Features

  • 1 to 1 FlexDeploy project per APEX project, whether you choose package-based or full deployment.

  • Full & Package-Based Deployment models.

  • Page and/or component level build and deploy/

  • Source application from development environment or SCM. Automatically export APEX application from development environment or source from SCM during build.

  • Selectively import entire application or individual pages and/or shared components.

  • Compare individual pages and/or components across all environments to find difference. Comparison is done against deployment state details in FlexDeploy.

  • Change detection during deployment, i.e. if application/page/component is already deployed (no changes) then it will skip. User can force deployment, if necessary, as well.

  • Continuous Integration use cases

    • Automated export of APEX application and commit to SCM of your choice to enable continuous integration.

    • As application is exported in split format, it is very easy to use SCM tools to view changes over time to individual page/component.

...