mirror of
https://github.com/apache/jclouds.git
synced 2026-09-01 00:44:28 +00:00
gurkerl83
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.
The jclouds provider for Amazon's S3 (http://aws.amazon.com/s3/)
Expects the jclouds s3 API to be present on your application's classpath.
- TODO: Implementation status.
- TODO: Supported features.
- TODO: Usage example.
Running live tests
Try
mvn clean install -Plive -pl :aws-s3 -Dtest=AWSS3ClientLiveTest -Dtest.aws-s3.identity=<aws_access_key_id> -Dtest.aws-s3.credential=<aws_secret_access_key>
optionally adding
-Dtest.aws-s3.sessionToken=<aws_session_token>