All Products
Search
Document Center

:Compatibility

Last Updated:Jul 18, 2023

Darabonba SDKs (V2.0) are not compatible with Classic SDKs (V1.0). To use Classic SDKs together with Darabonba SDKs, you can use different naming conventions for the two SDK versions when you add dependencies.

Darabonba SDKs are named in the ${Service name}${API version number} format. For example, the Darabonba SDK of Elastic Compute Service (ECS) is named com.aliyun:ecs20140526, and the Darabonba SDK of Virtual Private Cloud (VPC) is named com.aliyun:vpc20160428. To view the version number of an API, visit SDK Center.

The following code provides an example on how to add Maven dependencies on the Darabonba SDK of ECS and the Classic SDK of ECS:

<dependencies>
  <!--  V2.0 SDK  -->
  <dependency>
    <groupId>com.aliyun</groupId>
    <artifactId>ecs20140526</artifactId>
    <version>3.1.12</version>
  </dependency>
  <!--  V1.0 SDK  -->
  <dependency>
    <groupId>com.aliyun</groupId>
    <artifactId>aliyun-java-sdk-core</artifactId>
    <version>4.6.3</version>
  </dependency>
  <dependency>
    <groupId>com.aliyun</groupId>
    <artifactId>aliyun-java-sdk-ecs</artifactId>
    <version>4.24.59</version>
  </dependency>
</dependencies>