Release 1.5.0

defensive null checks

disable Javadoc generation cuz it won't work

name Fix

Squashed commit of the following:

commit bc18620
Author: Thanos Psaridis <psaridis@gmail.com>
Date:   Sun Apr 22 13:29:00 2018 +0300

    New Release 1.3.7

commit 281efe5
Author: Thanos Psaridis <psaridis@gmail.com>
Date:   Sat Apr 14 13:25:43 2018 +0300

    Added LocationUtils class for checking Location availability

commit 621e461
Author: Thanos Psaridis <psaridis@gmail.com>
Date:   Mon Apr 9 22:09:59 2018 +0300

    Reformatted code to classic Java style

commit 9f98ad6
Author: Thanos Psaridis <psaridis@gmail.com>
Date:   Mon Apr 9 22:07:02 2018 +0300

    Added overloaded `enableWifi()` method to avoid passing `null` to the old `enableWifi(null)` if one doesn't want to deal with callbacks

commit 8b291fe
Author: thanos psaridis <psaridis@gmail.com>
Date:   Mon Apr 9 21:57:48 2018 +0300

    Defensive null check for issue ThanosFisherman#8

commit cad2a51
Author: Thanos Psaridis <psaridis@gmail.com>
Date:   Mon Apr 9 21:43:00 2018 +0300

    Updated gradle-android plugin

🐛 Fixes the issue "ConnectionSuccessListener always returns successfu…

…l" (ThanosFisherman#9)

Why is this change needed?
   To fix the false positive for the wifi connection

How does it address the issue?
   Only returns success when the connection with the hotspot is made successfully after authentication process (SupplicantState.COMPLETED), and checks if we received the ip from the network. This prevents the scenario that the authentication process returns success, but with the connection in state "Obtaining ip address".

Release 1.3.5

Don't clear network config on failure plus new Release 1.3.4

Release 1.3.3

Release 1.3.2 Implemented canceling auto connect feature plus some ot…

…her auto connect fixes