This is the recommended way with Erlang.mk.
By default, the version is inherited from rabbitmq-server-release when
the source archive is created, or computed from git-describe(1) (see
`rabbitmq-components.mk`). One can override the version from the command
line by setting the `PROJECT_VERSION` variable.
[#130992027]
- use the private directory for the test run instead of TMPDIR
- use dynamic TCP port allocation
- get hostname from test configuration
- do not use hardcoded tcp port numbers
- don't test for the existence of the whitelist directory
- increase test timeout
- create test dir per test case
- use ct groups
- use a subdirectory of the certs directory for trust store certs
Fixes#29.
Loïc Hoguin has done a lot of helpful work around the PKI + SLL
applications in OTP to build certificates, authorities, and more all
through Erlang, so no calls from the command-line necessary. At the
end of the day they'd use the same stuff behind the scenes: Open
SLL. But, these make it extreamly convenient to test changes in Rabbit
revolving around TLS + certificates.