Put v0.1.0 on maven central about secure-preferences HOT 9 CLOSED

Yes, you're right, published this morning and also tagged and uploaded aar to github releases. Will close this once changes are propagated to all servers.

from secure-preferences.

it's available on maven central now. You can update your doc in confidence and then you're good to close this issue!

from secure-preferences.

Btw, guys, it's also very easy to get the latest GitHub release with JitPack.io. No need to upload anything. Here's v0.1.0: https://jitpack.io/#scottyab/secure-preferences/v0.1.0 : )

from secure-preferences.

Even if v0.1.0 is on Maven Central, how do you handle aes-crypto dependency?
I end up getting: Could not find com.scottyab:aes-crypto:0.0.2-SNAPSHOT. and, as a matter of fact, it is not in Maven Central.

from secure-preferences.

For time being, add

repositories {
    maven {
        url "https://oss.sonatype.org/content/repositories/snapshots"
    }
}

dependencies {
    // Secured preferences
    compile 'com.scottyab:aes-crypto:0.0.2-SNAPSHOT'
    compile('com.scottyab:secure-preferences-lib:0.1.0') {
        provided 'com.scottyab:aes-crypto:0.0.2-SNAPSHOT'
    }
}

from secure-preferences.

Apologies chaps, I'll sort that aes-crypto dependancy soon. It's my fork and I was waiting for the repo owner to accept my PR.

from secure-preferences.

Thank you Laimiux for your answer. Scott nice library, I think you should put Laimiux answer in the main page, because, most of us are using graddle and it will be easy meanwhile you sort the issues with the dependencies.

from secure-preferences.

Hey @gabrielacosta, done, but i'll need to go one better and sort it properly and remove the snapshot repo dependancy. I will just publish my fork to Maven Central as aes-crypto owner doesn't seem to have done that yet (even thought they have accepted my PR).

from secure-preferences.

This is all sync'd up correctly in v0.1.1

compile 'com.scottyab:secure-preferences-lib:0.1.1

from secure-preferences.