Allow users to choose their own jclouds modules with properties
---------------------------------------------------------------
Key: WHIRR-417
URL: https://issues.apache.org/jira/browse/WHIRR-417
Project: Whirr
Issue Type: Improvement
Reporter: Adrian Cole
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
