Due to how the `echo` statement adds a space character, the output marker was not found while parsing the output of `rabbitmq-env-conf.bat`. This, in turn, resulted in _none_ of the environment variables defined there being re-exported. In addition, the parsing of the output did not succeed as the default is to expect `sh`-style output. It is rare for users to use this file on Windows which is how this behavior has not been noticed in years. Related to: * https://pivotal-esc.atlassian.net/browse/VESC-1077 * https://vmware.slack.com/archives/C0RDGG81Z/p1689274725888439 * https://github.com/rabbitmq/rabbitmq-server/pull/5486 (tangentially related) Add some simple win32 parsing tests |
||
|---|---|---|
| .. | ||
| include | ||
| mk | ||
| src | ||
| test | ||
| .gitignore | ||
| BUILD.bazel | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| LICENSE-BSD-recon | ||
| LICENSE-MIT-Erlware-Commons | ||
| LICENSE-MIT-Mochi | ||
| LICENSE-MPL-RabbitMQ | ||
| Makefile | ||
| README.md | ||
| app.bzl | ||
| codegen.py | ||
| development.post.mk | ||
| development.pre.mk | ||
| erlang.mk | ||
| rabbitmq-components.mk | ||
README.md
RabbitMQ Common
This library is shared between RabbitMQ server, RabbitMQ Erlang client and other RabbitMQ ecosystem projects.