fixed jruby_version function
…e inject. We don't replace inject with fetch because then TorqueSpec could only be used with TorqueBox 2.1.0 or higher. We do replace inject with fetch in the README.org since fetch is the preferred way to use resource injection now.
* Logs through RSpec messages instead of farting out of $stdout all the time. * Adds the option to make it silent, in which case the output should look similar to vanilla RSpec (without torquespec). * Verbosity is ON by default (to behave as closely to the original as is reasonably possible). Note that this isn't exactly identical to the original, which was outputting through $stdout, not RSpec messages.
If a DOMAIN_MODE environment variable or a domain.mode system property is set, TorqueSpec will fire up a domain controller, hopefully configured with at least one host controller and one server group. There seems to be a problem with in-container testing interfering with results being relayed back to RSpec, so I'm disabling them when TorqueSpec.domain_mode is true. This effectively turns remote_describe into a no-op.
Upstream AS 7.1 builds no longer accept nor need a -logmodule argument.
The problem occurs when the client side lacks the class of the exception tossed by the server. Also don't think we need to fail_filtered_examples on the client since the server already did it.
…sons, apparently) I was adding the TorqueSpec::Daemon to a services block that already had one, but the write check was failing to detect that it was changed from the original. There's no real value from not always writing, I don't think.