Ali Ok Before we can continue with the other tasks (use the BOM in the Android SDK, create user docs) we need to have create it first. After some discussions we have decided to use the Aerogear Parent project (https://github.com/aerogear/aerogear-parent) as a host for the BOM. This project used to have an android BOM (for the old SDK presumably?) but it was removed: https://github.com/aerogear/aerogear-parent/pull/68

A BOM is a regular maven pom.xml that defines a dependencyManagement section. Another example can be found here: https://github.com/pb82/aerogear-android-sdk-bom. That's also the BOM used in the spike. We want to specify (lock down) the versions of all our dependencies (direct or transitive). Think of a package-lock.json in npm terms. This could be useful: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

We need to figure out the initial set of dependencies that we want to lock down. I'd suggest taking a look at the current dependencies of the android SDK, especially Summer's branch: https://github.com/secondsun/aerogear-android-sdk/tree/PoC to get an Idea. The BOM will be extended as we add dependencies to the SDK.

After an initial BOM is defined we need to (re)publish the aerogear parent project. For this we need to talk to Matthias Wessendorf