erlang:test-release

Full name:

eu.lindenbaum:maven-erlang-plugin:2.2.0:test-release

Description:

This Mojo checks the release file for plausability. This is done by checking the release version, the release name as well as checking all dependencies for correct versioning and existence.

Attributes:

  • Requires a Maven project to be executed.
  • Requires dependency resolution of artifacts in scope: test.
  • Binds by default to the lifecycle phase: test.

Required Parameters

Name Type Since Description
otpRelease String -

This must be set to the Erlang/OTP release version this release will be based on. The version should be given as it would be returned by erlang:system_info(otp_release).

An extended syntax is allowed to express partial version matching, using a trailing wildcard character "*" (e.g. "R14B*") and optional version matching, using a pipe character "|" (e.g. "R14B04|R15B*"), matching either.

All standard OTP dependencies like kernel, stdlib, ... will be configured to the version of the configured Erlang/OTP release. In order to do this the executing backend node has to run the required OTP release. Release packaging will fail if the backend node doesn't do so unless the skipReleaseTest parameter is specified.

Optional Parameters

Name Type Since Description
cookie String - The cookie to use for the java and the backend node.
erlCommand String - The erlang command used to start an erlang backend node. The path must exist and the destination must be executable. If the given command does not fullfill these requirements erl is used (assuming the command is part of the hosts PATH). The path must not contain any arguments.
skipReleaseTest boolean - Setting this to true will will skip comparison of the OTP release version against the required OTP version. The release build will fail if the backend node doesn't run the required Erlang/OTP release specified by otpRelease.
Default value is: false.

Parameter Details

cookie:

The cookie to use for the java and the backend node.
  • Type: java.lang.String
  • Required: No
  • Expression: ${cookie}

erlCommand:

The erlang command used to start an erlang backend node. The path must exist and the destination must be executable. If the given command does not fullfill these requirements erl is used (assuming the command is part of the hosts PATH). The path must not contain any arguments.
  • Type: java.lang.String
  • Required: No
  • Expression: ${erlCommand}

otpRelease:

This must be set to the Erlang/OTP release version this release will be based on. The version should be given as it would be returned by erlang:system_info(otp_release).

An extended syntax is allowed to express partial version matching, using a trailing wildcard character "*" (e.g. "R14B*") and optional version matching, using a pipe character "|" (e.g. "R14B04|R15B*"), matching either.

All standard OTP dependencies like kernel, stdlib, ... will be configured to the version of the configured Erlang/OTP release. In order to do this the executing backend node has to run the required OTP release. Release packaging will fail if the backend node doesn't do so unless the skipReleaseTest parameter is specified.

  • Type: java.lang.String
  • Required: Yes
  • Expression: ${otpRelease}

skipReleaseTest:

Setting this to true will will skip comparison of the OTP release version against the required OTP version. The release build will fail if the backend node doesn't run the required Erlang/OTP release specified by otpRelease.
  • Type: boolean
  • Required: No
  • Expression: ${skipReleaseTest}
  • Default: false