mirror of https://github.com/apache/jclouds.git
3d753a48d2
- Mock-Webserver v2.2.0 - Vendor, defined dependency bcprov-jdk15on > Previously, the dependency got excluded; otherwise, it conflicted with the existing bouncy castle version used in JClouds. - Mock-Webserver v3.14.9 - The vendor does not define a bouncy castle dependency anymore; instead, it moved to the okhttp-tls module. - Introduce the okhttp-tls module for tests in the core module. The following APIs (Docker, Elastic-Stack) and providers Softlayer extend their respective MockTest from BaseMockWebServerTest. The mock base test is located in the test jar of JClouds core module. - Due to conflicting bouncy castle classes in the classpath, those which get loaded from the okhttp-tls module, and those defined in JClouds bouncy castle module, the bouncy castle dependency of okhttp-tls has to get skipped for the two APIs and providers mentioned. Side note: The JClouds GAE driver module also requires the new okhttp-tls dependency because of the following chain of inheritance. Different from the situation above, the bouncy castle classes of the okhttp-tls got not excluded. GaeHttpCommandExecutorServiceIntegrationTest -> BaseHttpCommandExecutorServiceIntegrationTest -> BaseMockWebServerTest The reason for this is unknown to me. |
||
---|---|---|
.. | ||
src | ||
README.txt | ||
bnd.bnd | ||
pom.xml |
README.txt
# # The jclouds provider for Amazon's EC2 (http://aws.amazon.com/ec2/). # # Expects the jclouds ec2 API to be present on your application's classpath. # # TODO: Implementation status. # TODO: Supported features. # TODO: Usage example.