Return-Path: X-Original-To: apmail-whirr-dev-archive@www.apache.org Delivered-To: apmail-whirr-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8554FDCD4 for ; Sat, 6 Oct 2012 15:15:03 +0000 (UTC) Received: (qmail 95945 invoked by uid 500); 6 Oct 2012 15:15:03 -0000 Delivered-To: apmail-whirr-dev-archive@whirr.apache.org Received: (qmail 95871 invoked by uid 500); 6 Oct 2012 15:15:02 -0000 Mailing-List: contact dev-help@whirr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@whirr.apache.org Delivered-To: mailing list dev@whirr.apache.org Received: (qmail 95858 invoked by uid 99); 6 Oct 2012 15:15:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Oct 2012 15:15:02 +0000 Date: Sat, 6 Oct 2012 15:15:02 +0000 (UTC) From: "Aled Sage (JIRA)" To: dev@whirr.apache.org Message-ID: <254590476.5152.1349536502595.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (WHIRR-666) Upgrade to jclouds 1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Aled Sage created WHIRR-666: ------------------------------- Summary: Upgrade to jclouds 1.5.1 Key: WHIRR-666 URL: https://issues.apache.org/jira/browse/WHIRR-666 Project: Whirr Issue Type: Bug Affects Versions: 0.8.0 Reporter: Aled Sage Fix For: 0.8.1 Now that jclouds 1.5.1 final release is available, it would be great to have a new release of whirr that uses this. brooklyncentral.github.com in particular would love this, as we make use of whirr - 0.8.0's dependency on jclouds 1.5.0-beta.10 makes it hard for us to upgrade brooklyn to the most recent jclouds. (This is related to WHIRR-593, where whirr was upgraded to 1.5.0-beta.11; but it looks like whirr 0.8.0 was released with 1.5.0-beta.10). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira