You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sdk/resourcemanager/README.md
+77-2Lines changed: 77 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ The services available via `azure-resourcemanager` are listed as below:
70
70
- SQL
71
71
- Storage
72
72
- Traffic Manager
73
-
- Search (preview)
73
+
- Search
74
74
</details>
75
75
76
76
In the case where you are interested in certain service above or the service not included in the multi-service package, you can choose to use the single-service package for each service. Those packages follow the same naming patterns and design principals. For example, the package for Media Services has the following artifact information.
@@ -157,7 +157,7 @@ The key concepts of Azure Management Libraries includes:
157
157
- Fluent interface to manage Azure resources.
158
158
- Dependency across Azure resources.
159
159
- Batch Azure resource provisioning.
160
-
- Integration with Azure role-based access control.
160
+
- Integration with [Azure role-based access control][rbac].
161
161
- Asynchronous operations with [Reactor][reactor]. (Preview)
162
162
- Configurable client, e.g. configuring HTTP client, retries, logging, etc.
[Azure Core][azure_core] (`azure-core`) is the shared library for all packages under `com.azure`.
361
+
It guarantees backward compatibility.
362
+
363
+
However, if one accidentally uses an older version of it via transitive dependencies, it might cause problem in runtime.
364
+
This case could happen when one module depends on multiple Azure Java SDKs with different versions, which in turn depends on different versions of `azure-core`.
365
+
366
+
Maven dependency plugin would help to diagnostic this problem.
0 commit comments