Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ace-dev@incubator.apache.org
Date: Wed, 19 Oct 2011 07:13:12 +0000 (UTC)
From: "Paul Bakker (Reopened) (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Message-ID: 
 <1955540216.9578.1319008392326.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1750378051.8101.1318975030967.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (ACE-187) AMIs can't be found because the search
 location is incorrect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Bakker reopened ACE-187:
-----------------------------


jclouds 1.2.1 has a dependency on sl4j. I added this to the pom (see patch). With sl4j it works again.
                
> 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: 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