On 19/01/2011, at 10:52 AM, Howard Lewis Ship wrote:
>> The common solution to this seems to be to populate properties in
>> ~/.gradle/gradle.properties and then source them like this:
>
> Eventually, I'm hoping to store this in a central file
> ~/.gradle/gradle.properties is fine) but encrypted. Perhaps Gradle can
> add some support for that ... maybe better than the broken Maven
> support!
Wouldn't that just be security through obscurity? The encryption has to be
reversible so you now have to protect the token that was used to encrypt the
password which is the same as the original problem, unless of course Gradle
doesn't decrypt automatically but asks you for the token to decrypt with but
then it may as well ask you for the password.
The best I have been able to come up with is just to ensure that the file
permissions on gradle.properties prevent other people from reading it.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
