Migration-guide.md

@@ -5,6 +5,32 @@ Please refer to each individual version step when migrating to a newer SDK. .x r
 
 The [[main integration document|Integration-guide]] always describes the most up-to-date integration requirements.
 
+## Upgrade to 1.6.0
+
+The SDK was split into a core part and a connection part specific to the Play Services library that the application wants to use. This allows, for example, to stay at Play Services 6.5 while still upgrading to the latest B4S version.
+
+Secondly, the SDK is now also released in .AAR format, next to the existing .JAR format. When Gradle is used as build system, it is strongly recommended to use the .AAR format as it no longer requires manually declaring B4S services in the Android Manifest.
+
+To upgrade **using Eclipse**, please ensure that the library dependencies are updated (refer to [the sample project `/libs` folder](https://github.com/ezeeworld/B4S-Android-SDK/tree/master/sample-eclipse/libs) for the full list). Then, from the [`/sdk/jar` release folder](https://github.com/ezeeworld/B4S-Android-SDK/tree/master/sdk/jar), add the latest `b4s-android-sdk.jar` file as well as the `b4s-android-sdk-playservicesXXX.jar` file. The version of the `-playservices` .JAR file should correspond to your Play Services version. For example, use `b4s-android-sdk-playservices650.jar` if you are at Play Services 6.5.X (v22).
+
+To upgrade **using Gradle**, start by removing the B4S services (and activities and broadcast receivers) from your `AndroidManifest.xml`. Next, remove the `b4s-android-sdk.jar` from your `/libs` folder and replace it with the `b4s-android-sdk.aar` and  `b4s-android-sdk-playservicesXXX.aar` .AAR files from the [`/sdk/aar` release folder](https://github.com/ezeeworld/B4S-Android-SDK/tree/master/sdk/aar). The version of the `-playservices` .JAR file should correspond to your Play Services version. For example, use `b4s-android-sdk-playservices830.jar` if you are at Play Services 8.3 (v28). Finally, in your root `/build.gradle` file, ensure that the libs directory is added to the `repositories` list. This part now looks something like:
+```groovy
+allprojects {
+    repositories {
+        jcenter()
+        flatDir{
+            dirs 'libs'
+        }
+    }
+}
+```
+Finally, in you applciations' `app/build.gradle` file, add the .AAR file dependencies, For example:
+```groovy
+    compile (name:'b4s-android-sdk', ext:'aar')
+    compile (name:'b4s-android-sdk-playservices830', ext:'aar')
+```
+See the [`sample-gradle` sample project](https://github.com/ezeeworld/B4S-Android-SDK/tree/master/sample-gradle) for an up-to-date configuration which uses Play Services 8.3.
+
 ## Upgrade to 1.5.5
 
 The Google Cloud Messaging (play-services-gcm) dependency is no longer a requirement if (and only if) push messaging is not used.