Attempted upgrade to fabric/crashlytics_v2.0.0
----------------------------------------------

Only works produces correct APK using maven (BUT only after we increased the android:targetSdkVersion from 11 to 19 in the AndroidManifest.xml, which means the menu won't work in the "classic" ProjectManagerActivity).
Eclipse building us broken because the produced APK is somehow missing the fabric/crashlytics libraries!

Other annoyances include:
 - the fabric eclipse plug-in installs 4(!) apklib projects in a kit-libs/ folder _inside_ the CollectorAndroid project, moving them elsewhere causes them to be re-added (no configuration possible)
 - the same plugin also seems to needslessly recreate the libs folder, which causes maven to trip over
    = this could be fixed by setting the nativeLibrariesDirectory parameter to libs in de android maven plugin config (but why, given that it is an empty dir?),
    = or by adding an ant task that deletes the folder at the start of the maven build (messy, what if it is not empty?)

FOR THESE REASONS WE POSTPONE UPGRADING TO fabric/crashlytics_v2.0.0...
We'll wait until either the fabric eclipse plugin (currently at v2.0.1) gets fixed (meaning working eclipse builds with crahslytics) and hopefully gets some configuration options.
OR (preferably) until we have a properly working way of loading AAR libraries in eclipse/ADT/m2e/m2e-android, in which case we can probably ditch the fabric eclipse plugin, or fool it into thinking we don't use crashlytics (so it doesn't install the kit-libs).

Signed-off-by: Matthias Stevens <matthias.stevens@gmail.com>