On 13/04/2012, at 10:26 PM, [email protected] wrote: > It might be nice to have a convention for a custom trust store to be used for > a build. That way the store could be checked in.
Ultimately, our credentials management will be able to source credentials from multiple locations (where 'credentials' here means both the stuff that the build uses to prove who it is to other parties, and that the build uses to verify other parties). My thought is that there won't be a baked in policy for where to get credentials, much like there isn't a baked in policy for where to get dependencies from. Instead, there will be something similar to the repository DSL, plus a bunch of plugins to add new types of providers, and some plugins to apply a convention over the top. So, it should definitely be easy to say in your build: "use the key store in $rootDir/$someConventionalLocation" - whatever form that takes. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
