Alternate approach to #502. At the level of S3, we are testing that the headers are actually applied, not trying to test the behavior of a specific JRE's HttpUrlConnection. Using OkHttp, we can decouple this test from flaking out in various environments. You can merge this Pull Request by running:
git pull https://github.com/adriancole/jclouds adrian.decouple-s3-mock-from-jre Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/545 -- Commit Summary -- * Rather than rely on or work around JRE behavior based, lock S3ClientMockTest using OkHttp. -- File Changes -- M apis/s3/pom.xml (6) M apis/s3/src/test/java/org/jclouds/s3/S3ClientMockTest.java (9) -- Patch Links -- https://github.com/jclouds/jclouds/pull/545.patch https://github.com/jclouds/jclouds/pull/545.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/545
