[
https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130439#comment-13130439
]
Adrian Cole commented on ACE-187:
---------------------------------
fwiw sshj is what has a slf4j dependency. Ex. if you use jsch there is no dep.
That said, I don't recommend using jsch :)
That said, the most sane setup for a computeservicecontext includes:
new SshjSshClientModule() [org.jclouds.driver/jclouds-sshj], new
EnterpriseConfigurationModule() [org.jclouds.driver/jclouds-enterprise], new
Slf4jLoggingModule() [org.jclouds.driver/jclouds-slf4j]
This will result in the most coherent configuration with the most thread-safe
libraries.
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: Added_sl4j_dependency.patch, jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by
> Ace. This is because jclouds now searches AMIs that already exist in the list
> of instances instead of in the general AMI directory. I fixed this by
> upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an
> deprecated and obsolete property where the ComputeServiceContextFactory is
> created.
--
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
