Github user erikdw commented on the issue:
https://github.com/apache/storm/pull/2433
@HeartSaVioR : really @revans2 noticed the change's implications for
storm-on-mesos, so he should get the credit. :-) He's rightly suggested that
we create some tests to codify everything that might break us -- that is
understandably difficult, but I'm collecting a list of things we'll need to
test for.
And awesome, `-c supervisor.thrift.port=<port>` will work great for us,
thanks for confirming! (I was able to look through the `bin/storm.py` code and
see that the `-c/--config` handling ends up putting elements into
`-Dstorm.options=` for any executed storm java class.)
---
