It is not a security problem. Storing passwords anywhere on the local system is an equal security problem, outside of password managers and keychains of some sort.
On Wed, Jul 16, 2014 at 5:31 AM, Shadowburst <[email protected]> wrote: > On Tuesday, 15 July 2014 15:02:32 UTC+1, Nick Stanchenko wrote: >> >> This suggests that building after a config change doesn't always rebuild >>> everything it ought to, which is very worrying. >>> >> >> Do you call reload after changing the build file? >> > Yes, but I've been making lots of changes, so it's not impossible that I > missed it one time. > > Thanks for your help, everyone, I've got my project building in debug mode > now. I can't manage to get it to sign a release for me though: it stops > with > > [warn] Package needs signing: burly-release-unsigned.apk > [warn] Package needs signing and zipaligning: burly-release-unsigned.apk > > From the README it looks like android-sdk-plugin will only sign if the > keystore password is stored in local.properties. (I've already put all the > non-sensitive information in there.) Is that true? That's a security > problem I can't live with. > > -- > You received this message because you are subscribed to the Google Groups > "scala-on-android" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
