[WHIRR-417] Allow users to choose their own jclouds modules with properties

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 0.7.0
• Assignee: Adrian Cole (Inactive)
• Reporter: Adrian Cole (Inactive)
• Created: 30/Oct/11 08:08
• Updated: 07/Nov/11 20:46
• Resolved: 07/Nov/11 20:46

Description

Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.

I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:

jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2

With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.