build/tests: tests.ssl=false now works

[dsmiley]

... but honor @RandomizeSSL(1.0)

[hossman]

+1

[hossman]

I don't know if this is a good idea or a terrible idea, but it just occurred to me -- should we do something like...

// a test can configure @RandomizeSSL(0.0) or with 1.0, and we must honor that.
final String sslProp = System.getProperty("tests.ssl");
if ("true".equals(sslProp)) {
  assumeFalse("tests.ssl=true but test does not support SSL", ssl == 0.0)
  return new SSLTestConfig(true, useClientAuth);
} else if ("false".equals(sslProp)) {
  assumeFalse("tests.ssl=false but test requires SSL", ssl == 1.0)
  return new SSLTestConfig(false, false);
}

?

[dsmiley]

I took you idea and tested it both ways. One test needed better recovery.