diff --git a/README.md b/README.md index c29576fe24..c4b53b7a32 100644 --- a/README.md +++ b/README.md @@ -2,9 +2,9 @@ # commercetools sync [![Build Status](https://travis-ci.org/commercetools/commercetools-sync-java.svg?branch=master)](https://travis-ci.org/commercetools/commercetools-sync-java) [![codecov](https://codecov.io/gh/commercetools/commercetools-sync-java/branch/master/graph/badge.svg)](https://codecov.io/gh/commercetools/commercetools-sync-java) -[![Benchmarks 3.0.0](https://img.shields.io/badge/Benchmarks-3.0.0-orange.svg)](https://commercetools.github.io/commercetools-sync-java/benchmarks/) +[![Benchmarks 3.0.1](https://img.shields.io/badge/Benchmarks-3.0.1-orange.svg)](https://commercetools.github.io/commercetools-sync-java/benchmarks/) [![Download](https://api.bintray.com/packages/commercetools/maven/commercetools-sync-java/images/download.svg) ](https://bintray.com/commercetools/maven/commercetools-sync-java/_latestVersion) -[![Javadoc](http://javadoc-badge.appspot.com/com.commercetools/commercetools-sync-java.svg?label=Javadoc)](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/) +[![Javadoc](http://javadoc-badge.appspot.com/com.commercetools/commercetools-sync-java.svg?label=Javadoc)](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/) [![Known Vulnerabilities](https://snyk.io/test/github/commercetools/commercetools-sync-java/4b2e26113d591bda158217c5dc1cf80a88665646/badge.svg)](https://snyk.io/test/github/commercetools/commercetools-sync-java/4b2e26113d591bda158217c5dc1cf80a88665646) More at https://commercetools.github.io/commercetools-sync-java @@ -40,7 +40,7 @@ The library supports synchronising the following entities in commercetools - [Ivy](#ivy) - [Roadmap](#roadmap) - [Release Notes](/docs/RELEASE_NOTES.md) -- [Javadoc](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/) +- [Javadoc](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/) - [Benchmarks](https://commercetools.github.io/commercetools-sync-java/benchmarks/) @@ -67,7 +67,7 @@ commercetools sync is a Java library that imports commercetools platform data in - Make sure you have `JDK 8` installed. - [commercetools-jvm-sdk](https://github.com/commercetools/commercetools-jvm-sdk) as a dependency in your JVM-based - application. (Make sure to use a version `>= 1.54.0`). + application. (Make sure to use a version `>= 1.55.0`). - a target commercetools project for syncing your source data to. @@ -82,24 +82,24 @@ Here are the most popular ones: com.commercetools commercetools-sync-java - 3.0.0 + 3.0.1 ```` #### Gradle ````groovy -implementation 'com.commercetools:commercetools-sync-java:3.0.0' +implementation 'com.commercetools:commercetools-sync-java:3.0.1' ```` #### SBT ```` -libraryDependencies += "com.commercetools" % "commercetools-sync-java" % "3.0.0" +libraryDependencies += "com.commercetools" % "commercetools-sync-java" % "3.0.1" ```` #### Ivy ````xml - + ```` diff --git a/docs/README.md b/docs/README.md index 4fd8b34105..01c07b47f6 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2,9 +2,9 @@ # commercetools sync [![Build Status](https://travis-ci.org/commercetools/commercetools-sync-java.svg?branch=master)](https://travis-ci.org/commercetools/commercetools-sync-java) [![codecov](https://codecov.io/gh/commercetools/commercetools-sync-java/branch/master/graph/badge.svg)](https://codecov.io/gh/commercetools/commercetools-sync-java) -[![Benchmarks 3.0.0](https://img.shields.io/badge/Benchmarks-3.0.0-orange.svg)](https://commercetools.github.io/commercetools-sync-java/benchmarks/) +[![Benchmarks 3.0.1](https://img.shields.io/badge/Benchmarks-3.0.1-orange.svg)](https://commercetools.github.io/commercetools-sync-java/benchmarks/) [![Download](https://api.bintray.com/packages/commercetools/maven/commercetools-sync-java/images/download.svg) ](https://bintray.com/commercetools/maven/commercetools-sync-java/_latestVersion) -[![Javadoc](http://javadoc-badge.appspot.com/com.commercetools/commercetools-sync-java.svg?label=Javadoc)](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/) +[![Javadoc](http://javadoc-badge.appspot.com/com.commercetools/commercetools-sync-java.svg?label=Javadoc)](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/) [![Known Vulnerabilities](https://snyk.io/test/github/commercetools/commercetools-sync-java/4b2e26113d591bda158217c5dc1cf80a88665646/badge.svg)](https://snyk.io/test/github/commercetools/commercetools-sync-java/4b2e26113d591bda158217c5dc1cf80a88665646) @@ -58,18 +58,18 @@ Here are the most popular ones: com.commercetools commercetools-sync-java - 3.0.0 + 3.0.1 ```` #### Gradle ````groovy -implementation 'com.commercetools:commercetools-sync-java:3.0.0' +implementation 'com.commercetools:commercetools-sync-java:3.0.1' ```` #### SBT ```` -libraryDependencies += "com.commercetools" % "commercetools-sync-java" % "3.0.0" +libraryDependencies += "com.commercetools" % "commercetools-sync-java" % "3.0.1" ```` #### Ivy ````xml - + ```` diff --git a/docs/RELEASE_NOTES.md b/docs/RELEASE_NOTES.md index c9cdebe271..1e136668f8 100644 --- a/docs/RELEASE_NOTES.md +++ b/docs/RELEASE_NOTES.md @@ -27,8 +27,8 @@ 7. Add Migration guide section which specifies explicitly if there are breaking changes and how to tackle them. --> - +- 🛠️ **Dependency Updates** (1) + - `commercetools-jvm-sdk` `1.54.0` -> [`1.55.0`](http://commercetools.github.io/commercetools-jvm-sdk/apidocs/io/sphere/sdk/meta/ReleaseNotes.html#v1_55_0) + ### 3.0.0 - Nov 18, 2020 [Commits](https://github.com/commercetools/commercetools-sync-java/compare/2.3.0...3.0.0) | [Javadoc](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/) | diff --git a/docs/usage/CART_DISCOUNT_SYNC.md b/docs/usage/CART_DISCOUNT_SYNC.md index 5428e83899..f192c9d28b 100644 --- a/docs/usage/CART_DISCOUNT_SYNC.md +++ b/docs/usage/CART_DISCOUNT_SYNC.md @@ -26,7 +26,7 @@ against a [CartDiscountDraft](https://docs.commercetools.com/http-api-projects-c #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `CartDiscountDraft`s that have their `key` fields set to be matched with @@ -37,7 +37,7 @@ fields set, otherwise they won't be matched. Types are matched by their `key`s. Therefore, in order for the sync to resolve the actual ids of the type reference, the `key` of the `Type` has to be supplied. - - When syncing from a source commercetools project, you can use [`mapToCartDiscountDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/cartdiscounts/utils/CartDiscountReferenceResolutionUtils.html#mapToCartDiscountDrafts-java.util.List-) + - When syncing from a source commercetools project, you can use [`mapToCartDiscountDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/cartdiscounts/utils/CartDiscountReferenceResolutionUtils.html#mapToCartDiscountDrafts-java.util.List-) method that maps from a `CartDiscount` to `CartDiscountDraft` in order to make them ready for reference resolution by the sync: ````java diff --git a/docs/usage/CATEGORY_SYNC.md b/docs/usage/CATEGORY_SYNC.md index 28503b62cd..5e5b45de2e 100644 --- a/docs/usage/CATEGORY_SYNC.md +++ b/docs/usage/CATEGORY_SYNC.md @@ -27,7 +27,7 @@ against a [CategoryDraft](https://docs.commercetools.com/http-api-projects-categ #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `CategoryDraft`s that have their `key` fields set to be matched with @@ -38,7 +38,7 @@ otherwise they won't be matched. These references are matched by their `key`s. Therefore, in order for the sync to resolve the actual ids of the references, their `key`s has to be supplied. - - When syncing from a source commercetools project, you can use [`mapToCategoryDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/categories/utils/CategoryReferenceResolutionUtils.html#mapToCategoryDrafts-java.util.List-) + - When syncing from a source commercetools project, you can use [`mapToCategoryDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/categories/utils/CategoryReferenceResolutionUtils.html#mapToCategoryDrafts-java.util.List-) method that maps from a `Category` to `CategoryDraft` in order to make them ready for reference resolution by the sync: ````java final List categoryDrafts = CategoryReferenceResolutionUtils.mapToCategoryDrafts(categories); diff --git a/docs/usage/CUSTOMER_SYNC.md b/docs/usage/CUSTOMER_SYNC.md index 405596042a..ff8ab2cc30 100644 --- a/docs/usage/CUSTOMER_SYNC.md +++ b/docs/usage/CUSTOMER_SYNC.md @@ -26,7 +26,7 @@ against a [CustomerDraft](https://docs.commercetools.com/api/projects/customers# #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `CustomerDraft`s that have their `key` fields set to be matched with customers in the @@ -43,7 +43,7 @@ Any reference that is not expanded will have its id in place and not replaced by resources on the target commercetools project and the library will issue an update/create an API request without reference resolution. - - When syncing from a source commercetools project, you can use [`mapToCustomerDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/customers/utils/CustomerReferenceResolutionUtils.html#mapToCustomerDrafts-java.util.List-) + - When syncing from a source commercetools project, you can use [`mapToCustomerDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/customers/utils/CustomerReferenceResolutionUtils.html#mapToCustomerDrafts-java.util.List-) method that maps from a `Customer` to `CustomerDraft` to make them ready for reference resolution by the sync: ````java diff --git a/docs/usage/CUSTOM_OBJECT_SYNC.md b/docs/usage/CUSTOM_OBJECT_SYNC.md index dd576096a8..3dcf569a5f 100644 --- a/docs/usage/CUSTOM_OBJECT_SYNC.md +++ b/docs/usage/CUSTOM_OBJECT_SYNC.md @@ -24,7 +24,7 @@ against a [CustomObjectDraft](https://docs.commercetools.com/http-api-projects-c #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `CustomObjectDraft`s that have their `key` and `container` fields set to be matched with diff --git a/docs/usage/IMPORTANT_USAGE_TIPS.md b/docs/usage/IMPORTANT_USAGE_TIPS.md index 0ba613aba1..3f70e275f3 100644 --- a/docs/usage/IMPORTANT_USAGE_TIPS.md +++ b/docs/usage/IMPORTANT_USAGE_TIPS.md @@ -31,7 +31,7 @@ productSync.sync(batch1) By design, scaling the sync process should **not** be done by executing the batches themselves in parallel. However, it can be done either by: - Changing the number of [max parallel requests](https://github.com/commercetools/commercetools-sync-java/tree/master/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L116) within the `sphereClient` configuration. It defines how many requests the client can execute in parallel. - - or changing the draft [batch size](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/commons/BaseSyncOptionsBuilder.html#batchSize-int-). It defines how many drafts can one batch contain. + - or changing the draft [batch size](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/commons/BaseSyncOptionsBuilder.html#batchSize-int-). It defines how many drafts can one batch contain. The current overridable default [configuration](https://github.com/commercetools/commercetools-sync-java/tree/master/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) of the `sphereClient` is the recommended good balance for stability and performance for the sync process. diff --git a/docs/usage/INVENTORY_SYNC.md b/docs/usage/INVENTORY_SYNC.md index fc5ed74d04..d7deefb855 100644 --- a/docs/usage/INVENTORY_SYNC.md +++ b/docs/usage/INVENTORY_SYNC.md @@ -27,7 +27,7 @@ against a [InventoryEntryDraft](https://docs.commercetools.com/http-api-projects #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `InventoryEntryDraft`s that have their `sku` fields set, @@ -37,7 +37,7 @@ If you have custom requirements for the sphere client creation, have a look into references are matched by their `key`s. Therefore, in order for the sync to resolve the actual ids of those references, their `key`s has to be supplied. - - When syncing from a source commercetools project, you can use [`mapToInventoryEntryDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/inventories/utils/InventoryReferenceResolutionUtils.html#mapToInventoryEntryDrafts-java.util.List-) + - When syncing from a source commercetools project, you can use [`mapToInventoryEntryDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/inventories/utils/InventoryReferenceResolutionUtils.html#mapToInventoryEntryDrafts-java.util.List-) method that that maps from a `InventoryEntry` to `InventoryEntryDraft` in order to make them ready for reference resolution by the sync: ````java final List inventoryEntryDrafts = InventoryReferenceResolutionUtils.mapToInventoryEntryDrafts(inventoryEntries); diff --git a/docs/usage/PRODUCT_SYNC.md b/docs/usage/PRODUCT_SYNC.md index 51eb6d0b7c..c1c92a64cf 100644 --- a/docs/usage/PRODUCT_SYNC.md +++ b/docs/usage/PRODUCT_SYNC.md @@ -27,7 +27,7 @@ against a [ProductDraft](https://docs.commercetools.com/http-api-projects-produc #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `ProductDraft`s that have their `key` fields set to be matched with @@ -41,7 +41,7 @@ all the variants in the target project are expected to have the `sku` fields set of the product also have prices, where each price also has some references including a reference to the `Type` of its custom fields and a reference to a `channel`. All these referenced resources are matched by their `key`s. Therefore, in order for the sync to resolve the actual ids of those references, those `key`s have to be supplied in the following way: - - When syncing from a source commercetools project, you can use [`mapToProductDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/products/utils/ProductReferenceResolutionUtils.html#mapToProductDrafts-java.util.List-) + - When syncing from a source commercetools project, you can use [`mapToProductDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/products/utils/ProductReferenceResolutionUtils.html#mapToProductDrafts-java.util.List-) method that maps from a `Product` to `ProductDraft` in order to make them ready for reference resolution by the sync: ````java final List productDrafts = ProductReferenceResolutionUtils.mapToProductDrafts(products); diff --git a/docs/usage/PRODUCT_TYPE_SYNC.md b/docs/usage/PRODUCT_TYPE_SYNC.md index 8a3e72ff2b..8608560433 100644 --- a/docs/usage/PRODUCT_TYPE_SYNC.md +++ b/docs/usage/PRODUCT_TYPE_SYNC.md @@ -29,7 +29,7 @@ against a [ProductTypeDraft](https://docs.commercetools.com/http-api-projects-pr #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `ProductTypeDraft`s that have their `key` fields set to be matched with @@ -42,7 +42,7 @@ references, those `key`s have to be supplied in the following way: - Provide the `key` value on the `id` field of the reference. This means that calling `getId()` on the reference would return its `key`. - **Note**: When syncing from a source commercetools project, you can use [`mapToProductTypeDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0 /com/commercetools/sync/producttypes/utils/ProductTypeReferenceResolutionUtils.html#mapToProductTypeDrafts-java.util.List-) + **Note**: When syncing from a source commercetools project, you can use [`mapToProductTypeDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1 /com/commercetools/sync/producttypes/utils/ProductTypeReferenceResolutionUtils.html#mapToProductTypeDrafts-java.util.List-) that replaces the references id fields with keys, in order to make them ready for reference resolution by the sync: ````java diff --git a/docs/usage/QUICK_START.md b/docs/usage/QUICK_START.md index 90373626d4..1ac23f88cb 100644 --- a/docs/usage/QUICK_START.md +++ b/docs/usage/QUICK_START.md @@ -20,35 +20,35 @@ com.commercetools.sdk.jvm.core commercetools-models - 1.54.0 + 1.55.0 com.commercetools.sdk.jvm.core commercetools-java-client - 1.54.0 + 1.55.0 com.commercetools.sdk.jvm.core commercetools-convenience - 1.54.0 + 1.55.0 com.commercetools commercetools-sync-java - 3.0.0 + 3.0.1 ```` - For Gradle users: ````groovy // Add commercetools-jvm-sdk dependencies. -implementation 'com.commercetools.sdk.jvm.core:commercetools-models:1.54.0' -implementation 'com.commercetools.sdk.jvm.core:commercetools-java-client:1.54.0' -implementation 'com.commercetools.sdk.jvm.core:commercetools-convenience:1.54.0' +implementation 'com.commercetools.sdk.jvm.core:commercetools-models:1.55.0' +implementation 'com.commercetools.sdk.jvm.core:commercetools-java-client:1.55.0' +implementation 'com.commercetools.sdk.jvm.core:commercetools-convenience:1.55.0' // Add commercetools-sync-java dependency. -implementation 'com.commercetools:commercetools-sync-java:3.0.0' +implementation 'com.commercetools:commercetools-sync-java:3.0.1' ```` ### 2. Setup Syncing Options diff --git a/docs/usage/SHOPPING_LIST_SYNC.md b/docs/usage/SHOPPING_LIST_SYNC.md index 2fc0212df6..88689714b7 100644 --- a/docs/usage/SHOPPING_LIST_SYNC.md +++ b/docs/usage/SHOPPING_LIST_SYNC.md @@ -44,7 +44,7 @@ Any reference that is not expanded will have its id in place and not replaced by resources on the target commercetools project and the library will issue an update/create an API request without reference resolution. Therefore, in order for the sync to resolve the actual ids of those references, those `key`s have to be supplied in the following way: - - When syncing from a source commercetools project, you can use [`mapToShoppingListDraft`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/shoppinglists/utils/ShoppingListReferenceResolutionUtils.html#mapToShoppingListDrafts-java.util.List-) + - When syncing from a source commercetools project, you can use [`mapToShoppingListDraft`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/shoppinglists/utils/ShoppingListReferenceResolutionUtils.html#mapToShoppingListDrafts-java.util.List-) method that maps from a `ShoppingList` to `ShoppingListDraft` to make them ready for reference resolution by the shopping list sync: ````java diff --git a/docs/usage/STATE_SYNC.md b/docs/usage/STATE_SYNC.md index 99a404f60b..3693bccaaf 100644 --- a/docs/usage/STATE_SYNC.md +++ b/docs/usage/STATE_SYNC.md @@ -27,7 +27,7 @@ against a [StateDraft](https://docs.commercetools.com/http-api-projects-states#s #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `StateDraft`s that have their `key` fields set to be matched with @@ -40,7 +40,7 @@ otherwise they won't be matched. transition would return its `key`. **Note**: When syncing from a source commercetools project, you can use this util which this library provides: - [`mapToStateDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.0/com/commercetools/sync/states/utils/StateReferenceResolutionUtils.html#mapToStateDrafts-java.util.List-) + [`mapToStateDrafts`](https://commercetools.github.io/commercetools-sync-java/v/3.0.1/com/commercetools/sync/states/utils/StateReferenceResolutionUtils.html#mapToStateDrafts-java.util.List-) that replaces the references id fields with keys, in order to make them ready for reference resolution by the sync: ````java // Puts the keys in the reference id fields to prepare for reference resolution diff --git a/docs/usage/TAX_CATEGORY_SYNC.md b/docs/usage/TAX_CATEGORY_SYNC.md index 6f3292e5e7..fd42ebf086 100644 --- a/docs/usage/TAX_CATEGORY_SYNC.md +++ b/docs/usage/TAX_CATEGORY_SYNC.md @@ -25,7 +25,7 @@ against a [TaxCategoryDraft](https://docs.commercetools.com/http-api-projects-ta #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `TaxCategoryDraft`s that have their `key` fields set to be matched with diff --git a/docs/usage/TYPE_SYNC.md b/docs/usage/TYPE_SYNC.md index b0e9cfa177..f8a0e44860 100644 --- a/docs/usage/TYPE_SYNC.md +++ b/docs/usage/TYPE_SYNC.md @@ -27,7 +27,7 @@ against a [TypeDraft](https://docs.commercetools.com/http-api-projects-types.htm #### Prerequisites 1. Create a `sphereClient`: -Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.0/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. +Use the [ClientConfigurationUtils](https://github.com/commercetools/commercetools-sync-java/blob/3.0.1/src/main/java/com/commercetools/sync/commons/utils/ClientConfigurationUtils.java#L45) which apply the best practices for `SphereClient` creation. If you have custom requirements for the sphere client creation, have a look into the [Important Usage Tips](IMPORTANT_USAGE_TIPS.md). 2. The sync expects a list of `TypeDraft`s that have their `key` fields set to be matched with diff --git a/mkdocs.yml b/mkdocs.yml index 787c143a20..c0ea1cbba8 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -61,7 +61,7 @@ nav: - Advanced: - Sync Options: usage/SYNC_OPTIONS.md - Usage Tips: usage/IMPORTANT_USAGE_TIPS.md - - Javadoc: https://commercetools.github.io/commercetools-sync-java/v/3.0.0/ + - Javadoc: https://commercetools.github.io/commercetools-sync-java/v/3.0.1/ - Release notes: RELEASE_NOTES.md - Roadmap: https://github.com/commercetools/commercetools-sync-java/milestones - Issues: https://github.com/commercetools/commercetools-sync-java/issues diff --git a/src/main/java/com/commercetools/sync/customers/utils/CustomerUpdateActionUtils.java b/src/main/java/com/commercetools/sync/customers/utils/CustomerUpdateActionUtils.java index d5d58d0c8d..8a1144c9f9 100644 --- a/src/main/java/com/commercetools/sync/customers/utils/CustomerUpdateActionUtils.java +++ b/src/main/java/com/commercetools/sync/customers/utils/CustomerUpdateActionUtils.java @@ -54,7 +54,6 @@ import static com.commercetools.sync.commons.utils.CommonTypeUpdateActionUtils.buildUpdateActionForReferences; import static java.lang.String.format; import static java.util.Collections.emptyList; -import static java.util.Collections.singletonList; import static java.util.function.Function.identity; import static java.util.stream.Collectors.toList; import static java.util.stream.Collectors.toMap;