http://forums.gradle.org/gradle/topics/tooling_api_not_using_gradle_properties
Long story short… 1. We don't allow any configuration of the trust manager that we use when talking https 2. The system properties that control the default trust manager are immutable and must be present on startup 3. The daemon doesn't manage these properties properly This is a pretty nasty situation. The only workaround for users I can think of is to mess with the JDK's default key store, which is not really practical with > 1 developer. Pointing this issue out in case we want to prioritise for 1.5. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
