Gradle version bump, changes/readme updated

scottyab · Jun 30, 2015 · 32cb0bf · 32cb0bf
1 parent e825d04
commit 32cb0bf
Show file tree

Hide file tree

Showing 7 changed files with 11 additions and 13 deletions.
diff --git a/README.md b/README.md
@@ -3,7 +3,7 @@ Secure-preferences
 
 [![Android Arsenal](https://img.shields.io/badge/Android%20Arsenal-secure--preferences-brightgreen.svg?style=flat)](http://android-arsenal.com/details/1/362)
 
-This is Android Shared preference wrapper that encrypts the values of Shared Preferences using AES 128, CBC, and PKCS5 padding with integrity checking in the form of a SHA 256 hash. Each key is stored as a one way SHA 256 hash. Both keys and values are base64 encoded before storing into prefs xml file. **By default the generated key is stored in the backing preferences file and so can be read and extracted by root user.** Recommend use the user password generated option as added in v0.1.0.
+This is Android Shared preference wrapper that encrypts the values of Shared Preferences using *AES 128*, *CBC*, and *PKCS5* padding with integrity checking in the form of a SHA 256 hash. Each key is stored as a one way SHA 256 hash. Both keys and values are base64 encoded before storing into prefs xml file. **By default the generated key is stored in the backing preferences file and so can be read and extracted by root user.** Recommend use the user password generated option as added in v0.1.0.
 
 The sample app is available on [playstore](https://play.google.com/store/apps/details?id=com.securepreferences.sample)
 
@@ -23,7 +23,7 @@ Maven central is the preferred way:
 
 ```java
 	dependencies {
-    	compile 'com.scottyab:secure-preferences-lib:0.0.4'
+    	compile 'com.scottyab:secure-preferences-lib:0.1.1'
 	}
 ```
 
@@ -45,7 +45,7 @@ You can define a separate file for encrypted preferences.
 ```
 
 
-##User password
+##User password - (recommended)
 Passing in a password to the SecurePreferences constructor means the key is generated at runtime and *not* stored in the backing pref file. 
 
 ```java

diff --git a/build.gradle b/build.gradle
@@ -4,7 +4,7 @@ buildscript {
         mavenCentral()
     }
     dependencies {
-        classpath 'com.android.tools.build:gradle:1.1.0'
+        classpath 'com.android.tools.build:gradle:1.2.3'
 
         // NOTE: Do not place your application dependencies here; they belong
         // in the individual module build.gradle files

diff --git a/changes.md b/changes.md
@@ -1,4 +1,8 @@
 ##Release Notes:
+0.1.1
+* Fixed build issue referencing 'com.scottyab:aes-crypto' dependency (previous pointed to snapshot repo)
+* Minor tweek to build file so doesn't error if you don't have the sample app signing config
+
 0.1.0
 This release is a major refactor of the guts of secure prefs, which is *Not backwards compatible* with 0.4.0 and older versions _yet!_. So if you have an existing app using this don't upgrade. I'll be looking to add migration into a later release.
 

diff --git a/docs/images/ss_playstore1.png b/docs/images/ss_playstore1.png
diff --git a/docs/images/ss_playstore2.png b/docs/images/ss_playstore2.png
diff --git a/gradle.properties b/gradle.properties
@@ -1,5 +1,5 @@
-VERSION_NAME=0.1.0-SNAPSHOT
-VERSION_CODE=10
+VERSION_NAME=0.1.1-SNAPSHOT
+VERSION_CODE=11
 GROUP=com.scottyab
 
 

diff --git a/library/build.gradle b/library/build.gradle
@@ -1,11 +1,5 @@
 apply plugin: 'com.android.library'
 
-repositories {
-    maven {
-        url "https://oss.sonatype.org/content/repositories/snapshots"
-    }
-}
-
 android {
     compileSdkVersion 21
     buildToolsVersion '21.1.2'
@@ -18,7 +12,7 @@ android {
     }
 
     dependencies {
-        compile 'com.scottyab:aes-crypto:0.0.2-SNAPSHOT'
+        compile 'com.scottyab:aes-crypto:0.0.2'
     }
 
     apply from: 'https://raw.github.com/chrisbanes/gradle-mvn-push/master/gradle-mvn-push.gradle'